Loopio

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established by hand on 2026-09-02. On 2026-09-04 the recorded URL was a reachable repository or package: a server you install and run on your own machine over stdio. Callable after an install, not a remote endpoint.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/fredericboyer/loopio-mcp (unofficial)

• https://github.com/fredericboyer/loopio-mcp

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• LOOPIO_API_BASE_PATH
  No
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_AUTH_NAME_CLAIM
  `name`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_AUTH_NAME_HEADER
  `x-ms-client-principal-name`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_AUTH_PRINCIPAL_HEADER
  `x-ms-client-principal`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_AUTH_ROLES_CLAIM
  `roles`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_CLIENT_ID
  Yes
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_CLIENT_SECRET
  Yes
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_HOST
  No
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_HTTP_ALLOWED_HOSTS
  `127.0.0.1:<port>,localhost:<port>`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_HTTP_HOST
  `0.0.0.0`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_HTTP_PORT
  `3000`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_MAX_RESULTS
  No
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_READ_ONLY
  No
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_SCOPES
  No
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• LOOPIO_TRUST_PROXY_AUTH
  `false`
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• Variable
  Required
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

api_gate, verbatim from the file:

enterprise-only. Loopio does not publish pricing; third-party procurement data (Vendr, aggregating 80+ verified purchases) puts entry pricing around $20,000/yr for the Foundations tier (10 seats), with typical ACVs of $15,000-$150,000+ depending on team size - a fully sales-led, quote-only model with no self-serve path or public API-pricing page found.

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/fredericboyer/loopio-mcp

No GitHub organisation could be tied to loopio.com with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

6 candidate accounts seen and rejected by the evidence rules: fredericboyer, Loopio-EPD, Avnio, loopio-app, Loopio-AI. A name match alone is never accepted; the account has to point at the vendor domain.

• Draft an RFP or questionnaire response

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://loopio.com/pricing/
• https://www.vendr.com/marketplace/loopio
• https://autorfp.ai/blog/loopio-pricing
• https://loopio.com/
• https://github.com/fredericboyer/loopio-mcp
• https://lobehub.com/mcp/fredericboyer-loopio-mcp
• https://loopio.com/platform/integrations/

7 source URLs. Raw sources field, verbatim:

https://loopio.com/pricing/, https://www.vendr.com/marketplace/loopio, https://autorfp.ai/blog/loopio-pricing, https://loopio.com/, https://github.com/fredericboyer/loopio-mcp, https://lobehub.com/mcp/fredericboyer-loopio-mcp, https://loopio.com/platform/integrations/

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.