# ai.thesingulariti/graviti (remote · graviti.thesingulariti.ai)

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

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `graviti.thesingulariti.ai`: 84/100 (this document), [markdown](https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp.md), [page](https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp)

## Channel facts

- Endpoint: `https://graviti.thesingulariti.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-thesingulariti-graviti 'https://graviti.thesingulariti.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-thesingulariti-graviti": {
      "url": "https://graviti.thesingulariti.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-thesingulariti-graviti": {
      "type": "http",
      "url": "https://graviti.thesingulariti.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-thesingulariti-graviti]
url = "https://graviti.thesingulariti.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-thesingulariti-graviti": {
      "type": "remote",
      "url": "https://graviti.thesingulariti.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-thesingulariti-graviti --url 'https://graviti.thesingulariti.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-thesingulariti-graviti:
    url: "https://graviti.thesingulariti.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-thesingulariti-graviti": {
      "Transport": "http",
      "Url": "https://graviti.thesingulariti.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-thesingulariti-graviti -t streamable-http -u 'https://graviti.thesingulariti.ai/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 84, +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.

### 2026-09-18 (score 83, +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.

### 2026-09-16 (score 82, +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.

### 2026-09-14 (score 81, +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.

### 2026-09-12 (score 80, +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.

### 2026-09-09 (score 79, +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.

### 2026-09-08 (score 78, 0)

- [security] 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
- [functional regression] Schema quality: 160 → 187
- [cosmetic] “report_conversion” added an optional parameter “offer_code”

### 2026-09-06 (score 78, +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.

## MCP tools (7)

### `match_intent` (~236 tokens)

Match buyer intent to brands

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.

Input parameters:

- `intent_profile` (string): Buyer intent voice; inferred from the question if omitted
- `question` (string, required): The buyer's question, as they phrased it

### `get_verified_claims` (~185 tokens)

Get claims with provenance for a brand

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.

Input parameters:

- `brand` (string, required): Brand id or name, e.g. 'bioptimizers'

### `category_landscape` (~175 tokens)

Category comparison table

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.

Input parameters:

- `category` (string): Category id, e.g. 'magnesium-supplements' or 'cold-plunge'; omit for all categories

### `get_accountability_log` (~189 tokens)

Public 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.

### `get_ledger` (~78 tokens)

Integrity ledger (hash-chained, signed, Bitcoin-anchored)

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.

### `get_gap_report` (~144 tokens)

Brand gap report (brand intelligence)

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.

Input parameters:

- `brand` (string, required): Brand id or name, e.g. 'bioptimizers'

### `report_conversion` (~308 tokens)

Report an attributed conversion (demo stub)

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.

Input parameters:

- `agent_platform` (string, required): e.g. 'claude', 'chatgpt', 'perplexity'
- `brand_id` (string, required)
- `conversation_id` (string, required): 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, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 75
- 2026-08-28: 74
- 2026-08-27: 67
- 2026-08-26: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://graviti.thesingulariti.ai/api/mcp
- Repository: https://github.com/sclaytonmyosin/graviti-engine
- Website: https://graviti.thesingulariti.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-thesingulariti-graviti/api-mcp