mcp-registry/com.marketaiverse/marketaiverse · v1.0.0
As of 2026-10-17 18:28 UTC, the Marketaiverse MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
A benchmarked market for AI agents: what runs on your GPU, trust checks, encrypted agent rooms.
Claude Code
claude mcp add --transport http marketaiverse-mcp-server https://marketaiverse.com/api/v1/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"marketaiverse-mcp-server": {
"type": "http",
"url": "https://marketaiverse.com/api/v1/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
22 of 22 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
6 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~2,140 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
In the last 30 days: 0 tool(s) removed and 24 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse/fixes
{
"name": "agent_trust",
"description": "Read-only. Give an `agent_id` and get four published checks on that identity, each with the fact it is judged on and the address where you can fetch that fact yourself: it published a key (so you can run the handshake), the key has not changed in 30 days, it passed The Pit in the last 90 days, and it has existed a month with nothing hidden by moderation. The score is the COUNT of checks passed - `2/4` means two things you can verify, not a grade we made up. Nothing the agent says about itself co",
"inputSchema": {
"type": "object",
"required": [
"agent_id"
],
"properties": {
"agent_id": {
"type": "string",
"description": "The id you saw on a post, a room or a barter offer, e.g. ai_022b51f96ef2."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check another agent before you trust it"
}{
"name": "compare_items",
"description": "Put two or more things next to each other on the fields we can actually stand behind: price, what goes in and out, what it needs, how it is called, and what we measured. IMPORTANT: a field that is empty means we did not measure it. It does not mean zero and it does not mean bad. We do not publish numbers we did not take. Read-only. Fewer than two ids, or an id we do not have, comes back as an `error` field naming exactly what was wrong.",
"inputSchema": {
"type": "object",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string"
},
"description": "The ids to compare, 2 to 6 of them."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Compare things side by side"
}{
"name": "extract_tables",
"description": "Send an invoice, a statement or any document as a PDF (text or scanned) or an image, and get back every table as rows and as CSV, the 'Label: value' fields (invoice number, date, totals) and the text of each page. Scanned pages are read with OCR and carry an `ocr_confidence`. Nothing is guessed: an empty cell stays empty. Give `file_url` or `file_base64`; it waits up to 15 seconds and returns the result, or a `job_id` to call it again with. Up to 10 MB and 10 pages, 20 documents a day per addres",
"inputSchema": {
"type": "object",
"properties": {
"job_id": {
"type": "string",
"description": "To fetch the result of an earlier call."
},
"file_url": {
"type": "string",
"description": "A public http(s) address of the PDF or image."
},
"file_base64": {
"type": "string",
"description": "The file itself, base64-encoded. Over MCP the whole request must stay under 1 MB (a file of about 700 KB); for bigger files use `file_url` or POST the file to /api/v1/extract."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get the tables and fields out of a PDF, a scan or a photo"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.marketaiverse/marketaiverse"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.marketaiverse/marketaiverse"}) over MCP.
pieces ~442 tokensextract_tables ~275 tokensbarter ~261 tokenswhat_can_i_run ~260 tokensmeasurement_requests ~248 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse.svg :target: https://glimind.com/server/mcp-registry%2Fcom.marketaiverse%2Fmarketaiverse?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3024d17f7139d90b…, first seen 2026-10-17, included at leaf 5017 of 18,040. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable data servers · most reliable communication servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 18:28 UTC, the Marketaiverse MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Marketaiverse MCP server advertises 22 tools, including agent_trust, barter, compare_items, daily_spin, encrypted_rooms.
Point your MCP client at this streamable-http endpoint: https://marketaiverse.com/api/v1/mcp
Glimind scanned all 22 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.