Mahshar
REMOTE · MAHSHAR.XYZ
Free API discovery for AI agents; execution may require USDC/x402 payments on Arc Mainnet.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 450 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 62
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 4 Nov 2026 · Probed https://mahshar.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mahshar.xyz | CN=YR1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 6198f0a82f49a4228133405961d7394b8b8 |
| SANs: mahshar.xyz | ||||||
| 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 mahshar.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| mahshar.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 400 |
| 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://mahshar.xyz/api/mcp | Verified | 200 | |
| http (plaintext) | http://mahshar.xyz/api/mcp | HTTPS enforced | 308 | https://mahshar.xyz/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 →
execute_api_call Execute a Mahshar API call ~280
Paid execution uses two calls to this same tool. First call without payment_signature and without prepared_call_token; the result returns status payment_required, the live payment challenge, a prepared_call_token, and normalized prepared-call arguments. Sign only that returned challenge externally with the caller's own wallet. Then call this same tool again with identical API/call arguments plus the exact returned prepared_call_token and the externally generated payment_signature; do not change any call argument between calls. Mahshar never accepts private keys, never signs on behalf of the caller, and never custodies buyer funds. If a signed submission returns transport_outcome_unknown, do not create a fresh authorization. Use get_purchase_response with the returned purchase capability for durable response recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | string | yes | – |
| body | – | – | – |
| buyer_wallet | string | yes | – |
| path_values | object | – | – |
| payment_signature | string | – | Sensitive Payment-Signature generated externally by the caller wallet from the returned live challenge. Supply it only with the exact prepared_call_token; never provide a private key, and do not log… |
| prepared_call_token | string | – | Sensitive bearer value returned by the unsigned call. Supply this exact value only with payment_signature and identical API/call arguments; do not log or share it. |
| query_values | object | – | – |
No output schema declared.
No examples provided.
get_api Get Mahshar API ~30
Return the public Mahshar agent execution contract for one active listing.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | string | yes | – |
No output schema declared.
No examples provided.
get_purchase_response Recover a paid Mahshar API response ~105
Retrieve the exact durable response for one paid purchase using the purchase capability returned by paid execution. Recovery uses that bearer capability only and never falls back to a browser session. The capability is sensitive: do not log or share it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | string | yes | – |
| buyer_wallet | string | yes | – |
| purchase_access_token | string | yes | Bearer-sensitive purchase capability returned by paid execution. It authorizes recovery of that exact purchase response; do not log or share it. |
No output schema declared.
No examples provided.
search_apis Search Mahshar APIs ~35
Search or page public active Mahshar API listing summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Mahshar MCP server?
Mahshar is a hosted endpoint at https://mahshar.xyz/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 · mahshar.xyz
claude mcp add --transport http sharken3948-mahshar 'https://mahshar.xyz/api/mcp'
What is the Mahshar MCP server?
Mahshar is an MCP server listed in the public MCP registry as io.github.sharken3948/mahshar. Free API discovery for AI agents; execution may require USDC/x402 payments on Arc Mainnet. This page covers its hosted endpoint (https://mahshar.xyz/api/mcp).
Is the Mahshar MCP server safe to use?
Mahshar scores 65 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 Mahshar MCP server expose?
Mahshar exposes 4 tools: search_apis, get_api, execute_api_call, get_purchase_response. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.
Does the Mahshar MCP server require authentication?
Its publisher declares no required credentials for Mahshar. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Mahshar MCP server still maintained?
Mahshar is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.