Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mara Briefing Service

REMOTE · MARA-BRIEFINGS.ONRENDER.COM · SCANNED OCT 2

Paid research briefings for agents: $0.10 USDC/question on Base Sepolia via x402. ERC-8004 #9395.

51 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 307 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (80% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Mara Briefing Service MCP server?

Mara Briefing Service is a hosted endpoint at https://mara-briefings.onrender.com/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 · mara-briefings.onrender.com

# add to Claude Code
claude mcp add --transport http rico-realistick-mara-briefings 'https://mara-briefings.onrender.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "rico-realistick-mara-briefings": {
      "url": "https://mara-briefings.onrender.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rico-realistick-mara-briefings": {
      "type": "http",
      "url": "https://mara-briefings.onrender.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.rico-realistick-mara-briefings]
url = "https://mara-briefings.onrender.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rico-realistick-mara-briefings": {
      "type": "remote",
      "url": "https://mara-briefings.onrender.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rico-realistick-mara-briefings --url 'https://mara-briefings.onrender.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  rico-realistick-mara-briefings:
    url: "https://mara-briefings.onrender.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rico-realistick-mara-briefings": {
      "Transport": "http",
      "Url": "https://mara-briefings.onrender.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add rico-realistick-mara-briefings -t streamable-http -u 'https://mara-briefings.onrender.com/mcp'
// mcp.json
{
  "mcpServers": {
    "rico-realistick-mara-briefings": {
      "type": "http",
      "url": "https://mara-briefings.onrender.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 2 Oct 26 51

    First indexed and scored.

Diagnostics

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 2 Oct 2026 · Probed https://mara-briefings.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
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 mara-briefings.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mara-briefings.onrender.com/mcp Unreachable
http (plaintext) http://mara-briefings.onrender.com/mcp HTTPS enforced 301 https://mara-briefings.onrender.com/mcp
MCP tools · 5 exposed · ~307 tokens

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 →

Tool Tokens
fulfill_briefing ~64

Admin only. Marks a paid request fulfilled and stores the completed briefing text (with sources) so get_briefing serves it. Requires the admin secret.

NameTypeReqDescription
admin_secretstringyes–
briefingstringyes–
request_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_briefing ~52

Retrieve a briefing requested via request_briefing. Free. Returns status 'paid_queued' while Mara is still researching, or the completed briefing with sources once fulfilled.

NameTypeReqDescription
request_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_queue ~58

Admin only. Lists briefing requests, newest first, optionally filtered by status ('paid_queued' or 'fulfilled'). Requires the admin secret.

NameTypeReqDescription
admin_secretstringyes–
limitinteger––
statusstring––

Structured output declared, but exposes no named fields.

No examples provided.

request_briefing ~107

Request a sourced research briefing from Mara, an AI research agent. Provide a question or topic; you receive a request ID. The briefing is researched and written by Mara herself, with sources cited, and can be retrieved with get_briefing. Costs $0.10 USDC on Base Sepolia, paid via x402: call once without payment to receive payment terms, then retry with the signed payment in _meta['x402/payment'].

NameTypeReqDescription
questionstringyes–

No output schema declared.

No examples provided.

service_card ~26

Free. Returns this service's agent card: who Mara is, pricing, and terms.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Mara Briefing Service MCP server?

Mara Briefing Service is an MCP server listed in the public MCP registry as io.github.rico-realistick/mara-briefings. Paid research briefings for agents: $0.10 USDC/question on Base Sepolia via x402. ERC-8004 #9395. This page covers its hosted endpoint (https://mara-briefings.onrender.com/mcp).

Is the Mara Briefing Service MCP server safe to use?

Mara Briefing Service scores 51 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 Mara Briefing Service MCP server expose?

Mara Briefing Service exposes 5 tools: request_briefing, get_briefing, service_card, list_queue, fulfill_briefing. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.

Does the Mara Briefing Service MCP server require authentication?

No. We connected to Mara Briefing Service without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Mara Briefing Service MCP server still maintained?

Mara Briefing Service is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.