Graunt
REMOTE · API.GRAUNT.COM · SCANNED SEP 27
Find agent-ready data packets and check their rights, provenance and hashes before you use them.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 (good).Pass
- Tool/resource definitions use about 330 tokens (~36/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (22% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Graunt MCP server?
Graunt is a hosted endpoint at https://api.graunt.com/v1/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 · api.graunt.com
claude mcp add --transport http com-graunt-marketplace 'https://api.graunt.com/v1/mcp'
{
"mcpServers": {
"com-graunt-marketplace": {
"url": "https://api.graunt.com/v1/mcp"
}
}
} {
"servers": {
"com-graunt-marketplace": {
"type": "http",
"url": "https://api.graunt.com/v1/mcp"
}
}
} [mcp_servers.com-graunt-marketplace] url = "https://api.graunt.com/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-graunt-marketplace": {
"type": "remote",
"url": "https://api.graunt.com/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-graunt-marketplace --url 'https://api.graunt.com/v1/mcp' --transport streamable-http
mcp_servers:
com-graunt-marketplace:
url: "https://api.graunt.com/v1/mcp" {
"McpServers": {
"com-graunt-marketplace": {
"Transport": "http",
"Url": "https://api.graunt.com/v1/mcp"
}
}
} assistant mcp add com-graunt-marketplace -t streamable-http -u 'https://api.graunt.com/v1/mcp'
{
"mcpServers": {
"com-graunt-marketplace": {
"type": "http",
"url": "https://api.graunt.com/v1/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.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 27 Sept 2026 · Probed https://api.graunt.com/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.graunt.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 12 Sept 2026 | 28 Mar 2027 | RSA 2048 | SHA256-RSA | 1d61b2643fd60715c5fcf273d8e8e26 |
| SANs: api.graunt.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.graunt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| graunt.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.graunt.com/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.graunt.com/v1/mcp | HTTPS enforced | 301 | https://api.graunt.com:443/v1/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 →
fetch Read a Graunt packet ~40
Read one Graunt catalog packet by id. Returns its title, description, commercial terms, and public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The packet listing id. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_agent_commerce_manifest Read a listing's commercial terms ~36
Read the agent commerce manifest for a listing (D-269 v1 capability badges).
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
get_asset Read a catalog listing ~26
Read a single listing by id. Public projection.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
get_asset_manifest Read a listing's packet manifest ~28
Read the canonical asset manifest (sha256-stamped).
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
get_bundle_manifest Read a bundle's file inventory ~48
Read the per-asset bundle inventory: every delivered file with role, format, size and content hash, plus counts that name the population each one counted.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
meta_capabilities Read what Graunt offers ~24
Read /v1/meta/capabilities — the authoritative capability state map.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
meta_refinery_support_matrix Read supported packet source types ~22
Read /v1/meta/refinery-support-matrix.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search Search the Graunt catalog ~56
Search the Graunt catalog of evaluated data packets. Returns matching packets with their id, title, and public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results; default 20, cap 50. |
| query | string | yes | Search keywords. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_assets Search catalog listings ~50
Search the public catalog of evaluated packets and listings. Returns paginated matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows; default 20, cap 100. |
| q | string | – | Search query string. |
No output schema declared.
No examples provided.
What is the Graunt MCP server?
Graunt is an MCP server listed in the public MCP registry as com.graunt/marketplace. Find agent-ready data packets and check their rights, provenance and hashes before you use them. This page covers its hosted endpoint (https://api.graunt.com/v1/mcp).
Is the Graunt MCP server safe to use?
Graunt scores 72 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 Graunt MCP server expose?
Graunt exposes 9 tools: search, fetch, search_assets, get_asset, get_agent_commerce_manifest, and 4 more. Their descriptions and schemas cost roughly 330 tokens of context every time the server is loaded.
Does the Graunt MCP server require authentication?
No. We connected to Graunt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Graunt MCP server still maintained?
Graunt is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.