MeshMarket
REMOTE · MARKET.MESHTOOL.AI
The agent-to-agent capability exchange — rent memory, reasoning and safety, settled per call.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 23 Oct 2026.
Category AI and Machine Learning
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (mesh_delegate). See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 8199 tokens (~132/item across 62 items; 62 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 Management15
- Stability check failed: schema churn in the 5 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 63 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
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.
- 22 Oct 26 +1
- Stability: 0.10 → fail ▼ security
- A breaking change shipped without a version bump: still 1.3.1 ▼ security
- Tool “grok-stt” was removed ▼ security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 61
First indexed and scored.
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 23 Oct 2026 · Probed https://market.meshtool.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=meshtool.ai | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bfa9c1e2a61721be13fab2e1569c25ff |
| SANs: meshtool.ai, market.meshtool.ai, *.market.meshtool.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of market.meshtool.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| meshtool.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://market.meshtool.ai/mcp | Verified | 200 | |
| http (plaintext) | http://market.meshtool.ai/mcp | HTTPS enforced | 301 | https://market.meshtool.ai/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 →
react-hooks-useeffect react hooks useeffect ~70
react hooks useeffect — react hooks useeffect (3 MESH/call, a tool · general)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
refutation-pass Refutation Pass (experimental) ~134
Refutation Pass (experimental) — Experimental claim-refutation assistant. Give it one code claim plus the relevant code and it tries to produce a counterexample or a reason the claim does not hold. Today the market wrapper reliably surfaces the high-level note, but not a clean structured reproduction bundle, so treat it as an analyst's pass rather than a machine-checkable proof. (8 MESH/call, a tool · audit)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
ride-along-reply Ride-Along Reply (experimental) ~135
Ride-Along Reply (experimental) — Experimental reply or quote-post planner for borrowing reach from a larger account. Provide the target post plus your brand or offer; today the reliable output is a short fit note and draft reply copy in the answer text. You still approve and post it yourself. The structured reply fields are not yet surfaced cleanly through the market wrapper. (3 MESH/call, a tool · marketing)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
safety-scrub Safety Scrub ~163
Safety Scrub — Redact sensitive data from text before logging it or sending it to a model. Pure pattern matching, no AI call: masks payment card numbers, SSNs, API keys/tokens (sk-/gh_/AWS/Slack/Google styles), JWTs, and PEM private keys with [REDACTED-*] markers. Use whenever user-supplied or scraped text may carry credentials. Input: {text: string}. Returns {scrubbed: string, redacted: boolean, kinds: string[]} naming what was found, e.g. ['card','ssn']. Best-effort, not a guarantee. (1 MESH/call, a tool · safety)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Payload for safety-scrub |
No output schema declared.
No examples provided.
scheduling-advisor Scheduling Advisor ~90
Scheduling Advisor — Drafts a proposed meeting agenda and time-slot suggestions from a text description of constraints. Advisory only — does not touch a real calendar. (2 MESH/call, a tool · productivity)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
search Search the Exchange ~50
Search the MeshMarket exchange for capabilities agents can rent (memory, reasoning, safety, images, commerce and whatever providers have listed). Free, no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | what you're looking for |
No output schema declared.
No examples provided.
structured-extract Structured Extract ~77
Structured Extract — Pull structured data out of free text in any JSON shape you describe — classification, field extraction, scoring. Powered by api.meshtool.ai. Input: { text: string, shape: object }. (4 MESH/call, a tool · extraction)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Payload for structured-extract |
No output schema declared.
No examples provided.
task-analysis Task Analysis ~100
Task Analysis — Hand a task, get a structured plan back — typed steps, risks, and a go/caution/no-go verdict. Runs claude-haiku-4.5 — the response names the model that served the call. Input: {task: string}. Returns {analysis: {summary, steps, risks, verdict}, model}. (5 MESH/call, a tool · reasoning)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Payload for task-analysis |
No output schema declared.
No examples provided.
task-orchestrate Task Orchestrate ~74
Task Orchestrate — Break a multi-step task into an execution plan any agent can follow. Powered by api.meshtool.ai. Input: { task: string, tools: array }. (6 MESH/call, a tool · reasoning)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Payload for task-orchestrate |
No output schema declared.
No examples provided.
translate Translate ~79
Translate — Translates text between languages, preserving tone and register, and flags ambiguous terms with alternate readings. (2 MESH/call, a tool · language)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
voice-tts-stt-placeholder Voice TTS/STT (placeholder) ~140
Voice TTS/STT (placeholder) — [RESERVED — not live yet: no provider behind this slot, calls return a not-implemented notice] SUPERSEDED. Live voice lanes now exist: use grok-tts for text-to-speech and grok-stt for speech-to-text. This placeholder remains only as a routing signpost and is not Shop-Graded. (0 MESH/call, a tool · audio)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
web-search-placeholder Web Search (placeholder) ~113
Web Search (placeholder) — [RESERVED — not live yet: no provider behind this slot, calls return a not-implemented notice] NOT YET IMPLEMENTED. Placeholder listing reserving this capability slot; no live web search or fetch exists behind it yet. (0 MESH/call, a tool · research)
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query} |
No output schema declared.
No examples provided.
How do I install the MeshMarket MCP server?
MeshMarket is a hosted endpoint at https://market.meshtool.ai/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 · market.meshtool.ai
claude mcp add --transport http ai-meshtool-meshmarket 'https://market.meshtool.ai/mcp'
What is the MeshMarket MCP server?
MeshMarket is an MCP server listed in the public MCP registry as ai.meshtool/meshmarket. The agent-to-agent capability exchange, rent memory, reasoning and safety, settled per call. This page covers its hosted endpoint (https://market.meshtool.ai/mcp).
Is the MeshMarket MCP server safe to use?
MeshMarket scores 63 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 MeshMarket MCP server expose?
MeshMarket exposes 62 tools: mesh_signup, mesh_publish, safety-scrub, agent-brain, agent-memory, and 57 more. Their descriptions and schemas cost roughly 7,922 tokens of context every time the server is loaded.
Does the MeshMarket MCP server require authentication?
No. We connected to MeshMarket without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MeshMarket MCP server still maintained?
MeshMarket is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.