mcpbeat Sign in

Graviti MCP Server

by thesingulariti Your server? Claim it
not responding

Graviti is listed as active in the registry but did not answer our last check. It exposes 7 tools. Last commit 7 Sep 2026.

Verified brand claims with receipts for agent commerce. Ranking is never paid; the engine is open.

Uptime history 75 days of history · worst day 0%
75 days agonow
0.0%
Uptime 24h
0 of 92 checks
7
Tools
read from the server
104 ms
Response time
average over 24h
0
Stars
last commit 7 Sep 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.

7 Sep 4 tool descriptions were rewritten category_landscape, get_verified_claims, match_intent and 1 more
7 Sep a tool changed the parameters it asks for report_conversion
29 Aug 3 tool descriptions were rewritten category_landscape, match_intent, report_conversion
29 Aug a tool changed the parameters it asks for report_conversion
28 Aug a tool description was rewritten get_accountability_log
27 Aug a tool description was rewritten report_conversion

Graviti does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add graviti --transport http https://graviti.thesingulariti.ai/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://graviti.thesingulariti.ai/api/mcp
~/.codex/config.toml
[mcp_servers.graviti]
url = "https://graviti.thesingulariti.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "graviti": {
      "url": "https://graviti.thesingulariti.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "graviti": {
      "type": "http",
      "url": "https://graviti.thesingulariti.ai/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

accountability
get_accountability_log
Public, machine-readable log of every seal lifecycle change: flags, degradations, revocations, and restorations, with dates and reasons — plus confirmation-loop events (event: confirmation_request / confirmation_resolved), where the audit asked a brand to confirm a claim it couldn't re-verify: a visible ask, never a penalty. Also logged: claim_removed (a claim struck from a record, reason public), gap_report_delivered (a paid-tier report delivered to a brand, payment status disclosed — findings and rank never affected), and roster events (brand_added with lane/source, brand_removed, brand_declined, brand_skipped — every future change to who is in the index lands here per brand, reason public). The seal can be lost — a pulled seal is the loudest proof it means something. Payment can fast-track a re-evaluation; it can never change what it finds.
category
category_landscape
Comparison-table view of every brand in a category across disclosed attributes, with verification status marked per entry. Entries with captured ingredient/spec data also carry info_quality (0–100 disclosure completeness — transparency, never a rank factor; absent means not yet assessed, not zero). Every row carries evidence_state (audited / sourced / catalog_only); catalog_only rows are landscape presence only — never ranked or recommended. Rows include site_url and attributed_url (utm_source=graviti + signed gvt token — surface-level referral attribution, no user data); prefer attributed_url when linking. Rows with a published, receipt-backed discount code carry an offers array — disclosure only, never a ranking input.
gap
get_gap_report
What stands between a brand and top-of-category: attribute gaps vs the category leader, open flags, cohort blind spots per buyer-intent voice, and the ingredient/spec disclosure dimension — the brand's info_quality score with the exact publishable fixes that would raise it (publishing more truth, not paying Graviti). Demo of the paid brand-intelligence product — computed deterministically from the index; in production also draws on consented, compensated cohort signals (profiles never leave the user's agent). Catalog-only brands (no captured claims) receive an insufficient-evidence report instead of ranks.
ledger
get_ledger
Append-only version history of the index: each entry commits to the SHA-256 of the canonical index content and the previous entry's hash (rewriting history breaks every hash after it), is Ed25519-signed, and is anchored to Bitcoin via OpenTimestamps. Returns entries plus independent verification instructions. Even Graviti cannot rewrite the record.
match
match_intent
Takes a natural-language buyer question plus optional intent profile; returns recommendations ranked purely by fit score. Verification status is disclosed but never affects rank. Questions outside the verified index return an explicit out-of-scope result (in_index: false), never a guess. Brands without captured evidence (catalog_only) are returned in in_landscape_not_evidenced — listed, never scored, never recommended. Each recommendation carries the brand's site link twice: site_url (raw) and attributed_url (tagged utm_source=graviti + a signed gvt token, so the brand can verify the referral — surface-level only, no user data). Prefer attributed_url when linking. Where the brand publishes a discount code/promotion on its own pages, the entry carries an offers block (code, terms, verbatim-quote receipt, 14-day re-check window) — disclosure only: offers NEVER affect ranking, and a better deal never outranks a better fit.
report
report_conversion
Appends one attributed-transaction event to a log — the demo stub of the pay-on-real-acquisition loop. It moves no money, calls no external service, and never deletes or overwrites anything; the response states where (and whether) the event was persisted on this transport. Payment only ever flows on real transactions, never on impressions or rank. Optionally pass the gvt attribution token from the recommendation link that led to the purchase: it is verified against the published Ed25519 key and recorded with the event as verifiable provenance of the originating recommendation. Optionally pass offer_code if the buyer used a published code from the index's offers block, so deal-driven conversions are attributable — recorded as reported, never a rank input.
verified
get_verified_claims
Structured claims for one brand: provenance URLs, freshness timestamps, corroboration counts, and verification status (verified means the brand pays for auditing — always disclosed). Where captured, includes the specifications block (ingredient/spec disclosure with per-fact provenance) and its info_quality score — a 0–100 measure of disclosure completeness that never influences ranking. Graviti does not assess efficacy or clinical outcomes (not_assessed fence in every block). Claims with confirmation_status 'awaiting_brand_confirmation' are pending the brand's response to a re-verification ask — treat them as unconfirmed, not as violations. Where captured, an offers block lists the brand's published discount codes with receipts and full status history (active / expired / failed_verification) — disclosure only, never a ranking input.

Endpoints

URLTransportStateLatencyChecked
https://graviti.thesingulariti.ai/api/mcp streamable-http answering 104 ms 8 min ago

Alternatives to Graviti

same job, measured the same way
Kage
by kage-core

Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.

90 installs/wk local only
Bounty Engineer Agent Commerce
by gatoprd

Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.

22 tools answering
CrossingKey MCP
by crossingkeyintelligence

Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.

28 tools answering
P
ProofMart
by proofmart

One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.

3 tools answering
Yapitalism
by aytuncyildizli

Drive terminal coding agents by voice, with receipts that never claim more than they proved.

207 installs/wk local only
G
Glyt
by glyt

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

6 tools answering
Matchmaking rating for agent selection
by textforagents

Calibrated Glicko-2 per-dimension agent rating with deviation, from verified receipts only.

3 tools answering
Loop Desk
by bot2botlabs

Agent-payable open-loop tracker for refunds, returns, and asks with TRACE receipts.

3 tools answering

Graviti — questions

Answers built from our own checks of this server.

What can Graviti do?
It exposes 7 tools, read directly from the server on our last check. Among them: category_landscape, get_accountability_log, get_gap_report, get_ledger, get_verified_claims, match_intent and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Graviti working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 104 ms. The bar chart above shows every period we have measured.
The registry lists Graviti as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Graviti?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Graviti need an API key?
No. Graviti completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
Is Graviti open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at graviti.thesingulariti.ai, which runs on its operator's own terms.