MERCATOR Verify

io.github.ArzuoPublished by GitHub account Arzuov1.0.0Updated Oct 24, 2026

MERCATOR Verify: evidence-backed verification and decision support for autonomous agents.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up evidence-backed company facts, with field-level sources and explicit conflicts, and preflight a request before paying.

What you can do
The entity_evidence tool returns company facts for enrichment and verification, attaching field-level sources, freshness information and explicit conflicts; fields without evidence come back as UNKNOWN rather than a guess. The entity_evidence_validate tool is a free preflight that checks a request and shows the price and guarantees before any payment. It retrieves nothing and costs nothing.
When to use it
Useful when an assistant must verify or enrich company data and needs to show where each fact came from, or when you want to check a request and its price before committing to a paid call.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, API key or header is declared. Paid calls are billed through x402 at $0.10 per billable call, so a payment-capable client is needed for entity_evidence.
Before you install
entity_evidence costs $0.10 per billable call via x402, so an assistant can spend money; run the free validate preflight first. Results are third-party evidence and may contain conflicts or UNKNOWN fields, so verify before relying on them.

Installation

In SourceWeft

  1. Open MERCATOR Verify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Arzuo%2Fmercator-company-verification/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mercator-verify": {
      "type": "http",
      "url": "https://mercator-entity-evidence.fly.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

2

entity_evidence

Evidence-backed company facts and current company information for company enrichment and company verification, with field-level sources, freshness and explicit conflicts. Unevidenced fields return UNKNOWN rather than a guess. $0.10 per billable call via x402; a response adding nothing beyond the identifier you supplied is free.

Parametersnamedomainfieldsrequiredmax_age_days

entity_evidence_validate

FREE preflight for entity_evidence: check a request and see the price and guarantees before paying. Retrieves nothing and costs nothing.

Parametersnamedomainfieldsrequiredmax_age_days

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.