# Mahshar (remote · mahshar.xyz)

Free API discovery for AI agents; execution may require USDC/x402 payments on Arc Mainnet.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mahshar.xyz`: 65/100 (this document), [markdown](https://verifymcp.io/servers/sharken3948-mahshar/api-mcp.md), [page](https://verifymcp.io/servers/sharken3948-mahshar/api-mcp)

## Channel facts

- Endpoint: `https://mahshar.xyz/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 450 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add --transport http sharken3948-mahshar 'https://mahshar.xyz/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sharken3948-mahshar": {
      "url": "https://mahshar.xyz/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sharken3948-mahshar": {
      "type": "http",
      "url": "https://mahshar.xyz/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sharken3948-mahshar]
url = "https://mahshar.xyz/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sharken3948-mahshar --url 'https://mahshar.xyz/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sharken3948-mahshar:
    url: "https://mahshar.xyz/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sharken3948-mahshar": {
      "Transport": "http",
      "Url": "https://mahshar.xyz/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sharken3948-mahshar -t streamable-http -u 'https://mahshar.xyz/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sharken3948-mahshar": {
      "type": "http",
      "url": "https://mahshar.xyz/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-11-04 (score 65, +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.

### 2026-11-02 (score 64, +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.

### 2026-10-31 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 62)

First indexed and scored.

## MCP tools (4)

### `search_apis` (~35 tokens)

Search Mahshar APIs

Search or page public active Mahshar API listing summaries.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `get_api` (~30 tokens)

Get Mahshar API

Return the public Mahshar agent execution contract for one active listing.

Input parameters:

- `api_id` (string, required)

### `execute_api_call` (~280 tokens)

Execute a Mahshar API call

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.

Input parameters:

- `api_id` (string, required)
- `body`
- `buyer_wallet` (string, required)
- `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)

### `get_purchase_response` (~105 tokens)

Recover a paid Mahshar API response

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.

Input parameters:

- `api_id` (string, required)
- `buyer_wallet` (string, required)
- `purchase_access_token` (string, required): Bearer-sensitive purchase capability returned by paid execution. It authorizes recovery of that exact purchase response; do not log or share it.

## Diagnostics

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

## Score history

- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62

## Common questions

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

## Links

- Remote endpoint: https://mahshar.xyz/api/mcp
- Repository: https://github.com/sharken3948/Mahshar
- Website: https://mahshar.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/sharken3948-mahshar/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sharken3948-mahshar/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sharken3948-mahshar/api-mcp