ai.thesingulariti/graviti
REMOTE · GRAVITI.THESINGULARITI.AI · SCANNED SEP 21
Verified brand claims with receipts for agent commerce. Ranking is never paid; the engine is open.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1315 tokens (~187/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ai.thesingulariti/graviti MCP server?
ai.thesingulariti/graviti is a hosted endpoint at https://graviti.thesingulariti.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · graviti.thesingulariti.ai
claude mcp add --transport http ai-thesingulariti-graviti 'https://graviti.thesingulariti.ai/api/mcp'
{
"mcpServers": {
"ai-thesingulariti-graviti": {
"url": "https://graviti.thesingulariti.ai/api/mcp"
}
}
} {
"servers": {
"ai-thesingulariti-graviti": {
"type": "http",
"url": "https://graviti.thesingulariti.ai/api/mcp"
}
}
} [mcp_servers.ai-thesingulariti-graviti] url = "https://graviti.thesingulariti.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-thesingulariti-graviti": {
"type": "remote",
"url": "https://graviti.thesingulariti.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-thesingulariti-graviti --url 'https://graviti.thesingulariti.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-thesingulariti-graviti:
url: "https://graviti.thesingulariti.ai/api/mcp" {
"McpServers": {
"ai-thesingulariti-graviti": {
"Transport": "http",
"Url": "https://graviti.thesingulariti.ai/api/mcp"
}
}
} assistant mcp add ai-thesingulariti-graviti -t streamable-http -u 'https://graviti.thesingulariti.ai/api/mcp'
{
"mcpServers": {
"ai-thesingulariti-graviti": {
"type": "http",
"url": "https://graviti.thesingulariti.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Tool “category_landscape” rewrote its description, which is the text the model reads security
- Tool “get_verified_claims” rewrote its description, which is the text the model reads security
- Tool “match_intent” rewrote its description, which is the text the model reads security
- Tool “report_conversion” rewrote its description, which is the text the model reads security
- Schema quality: 160 → 187 ▼ functional
- “report_conversion” added an optional parameter “offer_code” cosmetic
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://graviti.thesingulariti.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=graviti.thesingulariti.ai | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 68f2e176b6f12ae844d185add1fbb32479d |
| SANs: graviti.thesingulariti.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of graviti.thesingulariti.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| thesingulariti.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://graviti.thesingulariti.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://graviti.thesingulariti.ai/api/mcp | HTTPS enforced | 308 | https://graviti.thesingulariti.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
category_landscape Category comparison table ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category id, e.g. 'magnesium-supplements' or 'cold-plunge'; omit for all categories |
No output schema declared.
No examples provided.
get_accountability_log Public accountability log ~189
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gap_report Brand gap report (brand intelligence) ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand id or name, e.g. 'bioptimizers' |
No output schema declared.
No examples provided.
get_ledger Integrity ledger (hash-chained, signed, Bitcoin-anchored) ~78
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verified_claims Get claims with provenance for a brand ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand id or name, e.g. 'bioptimizers' |
No output schema declared.
No examples provided.
match_intent Match buyer intent to brands ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_profile | string | – | Buyer intent voice; inferred from the question if omitted |
| question | string | yes | The buyer's question, as they phrased it |
No output schema declared.
No examples provided.
report_conversion Report an attributed conversion (demo stub) ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_platform | string | yes | e.g. 'claude', 'chatgpt', 'perplexity' |
| brand_id | string | yes | – |
| conversation_id | string | yes | Opaque id for the agent conversation that led to purchase |
| gvt | string | – | Optional: the gvt token from the attributed_url of the originating recommendation (gvt1.<surface>.<category>.<brand>.<date>.<sig>) — binds this conversion to a verifiable recommendation surface |
| offer_code | string | – | Optional: the published offer code the buyer applied (from the recommendation's offers block), e.g. 'WELCOME15' — attributes the conversion to a captured deal |
| order_value_usd | number | yes | – |
No output schema declared.
No examples provided.
What is the ai.thesingulariti/graviti MCP server?
ai.thesingulariti/graviti is an MCP server listed in the public MCP registry as ai.thesingulariti/graviti. Verified brand claims with receipts for agent commerce. Ranking is never paid; the engine is open. This page covers its hosted endpoint (https://graviti.thesingulariti.ai/api/mcp).
Is the ai.thesingulariti/graviti MCP server safe to use?
ai.thesingulariti/graviti scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.thesingulariti/graviti MCP server expose?
ai.thesingulariti/graviti exposes 7 tools: match_intent, get_verified_claims, category_landscape, get_accountability_log, get_ledger, and 2 more. Their descriptions and schemas cost roughly 1,315 tokens of context every time the server is loaded.
Does the ai.thesingulariti/graviti MCP server require authentication?
No. We connected to ai.thesingulariti/graviti without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.thesingulariti/graviti MCP server still maintained?
ai.thesingulariti/graviti is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.