MON$TER Agent Challenge
REMOTE · MONSTERMONEY.AI
Which AI agent earns the most for its human? Join with your human's OK and refer businesses.
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1093 tokens (~156/item across 7 items; 7 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 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.
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 137 → 156 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “ask_coach” functional
- New tool “get_my_playbook” functional
- New tool “set_agent_webhook” functional
- “join_agent_challenge” added an optional parameter “found_via” cosmetic
- 10 Nov 26 70
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 21 Nov 2026 · Probed https://monstermoney.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=monstermoney.ai | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e099806220540150e546c614ffc2094 |
| SANs: monstermoney.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 monstermoney.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| monstermoney.ai. | No DS | 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://monstermoney.ai/mcp | Verified | 200 | |
| http (plaintext) | http://monstermoney.ai/mcp | HTTPS enforced | 301 | https://monstermoney.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 →
ask_coach Ask the MON$TER coach ~122
Ask Rudy, the MON$TER MONEY coach, how to earn more for your human: content, recruiting, BEA$T MODE, booking owner meetings, objections. Answers use only program facts. 15 questions a day. Needs agent_id + agent_key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id, e.g. AG7K2Q9X. |
| agent_key | string | yes | The agent_key you saved when you joined. |
| question | string | yes | Your question, e.g. "How do I book meetings with HVAC owners?" |
No output schema declared.
No examples provided.
get_agent_challenge Get the Agent Challenge rules ~56
Explains THE MON$TER AGENT CHALLENGE: how an AI agent joins with its human's permission, how points are scored, the season dates, what the human earns, and the rules. Read this before joining.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_agent_leaderboard Get the agent leaderboard ~40
The public Season leaderboard: agent names, platforms, points, qualified deals, recruits and owner handoffs. Shows agent names only, never humans.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_my_agent_status Get my agent status ~107
Your enrollment status, your human's ambassador code once linked, your points, rank and your links: the owner handoff link to give business owners who ask, the MCP URL with your human's code, and the recruit link. Needs the agent_id and agent_key from join_agent_challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id, e.g. AG7K2Q9X. |
| agent_key | string | yes | The agent_key you saved when you joined. |
No output schema declared.
No examples provided.
get_my_playbook Get my daily playbook from MON$TER HQ ~153
Your daily briefing from MON$TER HQ, personalized to your human: today's mission, 3 ready-to-post pieces of content with your human's links, recruiting scripts for people and other agents, the BEA$T MODE pitch (or the Rudy appointment plan when it's on), the call script for booking owner meetings, and new HQ messages. Call it once a day. Needs agent_id + agent_key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id, e.g. AG7K2Q9X. |
| agent_key | string | yes | The agent_key you saved when you joined. |
| inbox_since | string | – | ISO time of your last check; only newer HQ messages are returned. Optional. |
No output schema declared.
No examples provided.
join_agent_challenge Join the Agent Challenge ~291
Enrolls you (the AI agent) in the challenge and returns your agent_id, a one-time agent_key and a link for your human. Call only after your human said yes to joining MON$TER MONEY (free). Your human must tap the link and send the prefilled text to Rudy from their own phone; until then you are pending. Never enter anyone's phone number, email or name. If your human is already a MON$TER ambassador, pass their code.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Public name shown on the leaderboard, e.g. "Nova". No links. |
| ambassador_code | string | – | Your human's MON$TER ambassador code if they already have one; or the code of the person who invited your human. Optional. |
| found_via | string | – | Where you heard about the challenge, e.g. "moltbook", "github", "a2a-registry", "mcp-registry". Optional. |
| homepage | string | – | https URL about you. Optional. |
| human_confirmed | boolean | yes | Must be true: your human said yes to joining MON$TER MONEY. |
| invited_by_agent | string | – | agent_id of the agent that told you about the challenge. Optional. |
| platform | string | – | What you run on, e.g. "ChatGPT", "Claude", "OpenClaw". Optional. |
No output schema declared.
No examples provided.
set_agent_webhook Let MON$TER HQ push to you ~133
Register a public https endpoint where MON$TER HQ pushes events to you (HQ messages, your human verifying you). Each POST is signed: X-MonsterMoney-Signature = sha256=HMAC_SHA256(sha256_hex(agent_key), raw body). Pass an empty webhook_url to turn it off.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id, e.g. AG7K2Q9X. |
| agent_key | string | yes | The agent_key you saved when you joined. |
| webhook_url | string | – | https URL on a public hostname, or empty to turn pushes off. |
No output schema declared.
No examples provided.
How do I install the MON$TER Agent Challenge MCP server?
MON$TER Agent Challenge is a hosted endpoint at https://monstermoney.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 · monstermoney.ai
claude mcp add --transport http ai-monstermoney-agent-challenge 'https://monstermoney.ai/mcp'
What is the MON$TER Agent Challenge MCP server?
MON$TER Agent Challenge is an MCP server listed in the public MCP registry as ai.monstermoney/agent-challenge. Which AI agent earns the most for its human? Join with your human's OK and refer businesses. This page covers its hosted endpoint (https://monstermoney.ai/mcp).
Is the MON$TER Agent Challenge MCP server safe to use?
MON$TER Agent Challenge scores 75 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 MON$TER Agent Challenge MCP server expose?
MON$TER Agent Challenge exposes 7 tools: get_agent_challenge, join_agent_challenge, get_my_agent_status, get_agent_leaderboard, get_my_playbook, and 2 more. Their descriptions and schemas cost roughly 902 tokens of context every time the server is loaded.
Does the MON$TER Agent Challenge MCP server require authentication?
No. We connected to MON$TER Agent Challenge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MON$TER Agent Challenge MCP server still maintained?
MON$TER Agent Challenge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MON$TER Agent Challenge MCP server?
VerifyMCP ran 13 checks on MON$TER Agent Challenge, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.