MCP.Market

Faro MCP server

online · 100% uptime
by vedux98·io.github.vedux98/faro·v1.2.0

Verify URLs, payees, and messages before acting: red/yellow/green trust verdicts for agents.

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Faro yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Faro tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 244ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 76 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Faro compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
343 ms
faster than 43% of 30,031 servers

Install Faro in Claude Code, Cursor or VS Code

claude mcp add --transport http faro https://mcp.farofinance.app/mcp
Add to Cursor

What the publisher says

From the Faro repository's README, as published. We do not edit it. Read it on GitHub

Faro

Check before an agent pays, clicks, or trusts.

Faro is a trust layer for AI agents and apps. You send a URL, payee, message, or agent-payment payload — Faro returns one clear answer: green, yellow, or red, a one-line reason, and what to do next (allow / warn / block / review).

This repo is the open interface (Apache-2.0): the verdict contract, client SDKs, and auditable payment-protocol adapters. Scoring and the reputation graph stay on Faro’s hosted API, so you can audit what leaves your process without forking a black-box engine.

Get an API key → farofinance.app

What can you do with this package?

Typical users: agent builders, wallet/checkout integrators, MCP app authors, and security teams who need a single red/yellow/green decision at the moment of action — not a dashboard full of raw threat intel.

Quick start

pip install faro-client
import asyncio, os
from faro_client import FaroClient

async def main() -> None:
    async with FaroClient(os.environ["FARO_API_KEY"]) as client:
        result = await client.verify_url("https://example.com")
        print(result.verdict, result.reason, result.recommended_action)
        # Branch: allow | warn | block | review
        if result.recommended_action == "block":
            raise SystemExit("blocked by Faro")

asyncio.run(main())
curl -s -X POST https://api.farofinance.app/v1/verify/url \
  -H "Authorization: Bearer $FARO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"value":"https://example.com"}'

TypeScript: see sdk/typescript/. Payment parsers (no engine inside): adapters/faro_agentpay/. Recipes: recipes/.

What’s in this repo

Why open / what’s closed

Open here: schema, SDKs, protocol adapters, recipes, MCP tool docs — so integrators and protocol ecosystems can cite and fork the interface.

Closed (hosted API): signal providers, scoring, reputation graph, prompts. Adapters stop at a documented seam: parse → artifacts → POST /v1/verify (or your own checks) → optional worst_of.

Trust, plainly

Hosted verifies can carry signed trust receipts and a transparency log (hashes and signatures — not your raw PII). Product docs: farofinance.app.

Roadmap / future scope

Shipped or in flight on the hosted product (not all of this lives in this public repo):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Faro: common questions

Is Faro MCP server safe?
Mostly: it is graded B (82/100). Read the Faro safety report
How do I install Faro?
It runs remotely at mcp.farofinance.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Faro need an API key?
Yes. The registry entry asks for Authorization.
Is Faro maintained?
The last commit was 115 days ago (2026-07-12). The latest release is v1.2.0.
Is Faro up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Faro compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 343 ms (faster than 43% of 30,031 servers). Full comparison.