makememoneynomistakes.ai: ERC-8004 agent reputation and fraud checks
REMOTE · MAKEMEMONEYNOMISTAKES.AI
Check before you hire or pay an ERC-8004 agent on Base: track record, reputation and fraud flags.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Crypto and Web3
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 not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3313 tokens (~150/item across 22 items; 19 tools + 3 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
- Structured output schemas are declared (95% 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
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.
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_pass” rewrote its description, which is the text the model reads security
- Tool “export” rewrote its description, which is the text the model reads security
- Tool “list_agents” rewrote its description, which is the text the model reads security
- Tool “pathways_routes” rewrote its description, which is the text the model reads security
- 22 Oct 26 +1
- Tool “pathways_delegates” rewrote its description, which is the text the model reads security
- Tool “pathways_session” rewrote its description, which is the text the model reads security
- 20 Oct 26 0
- Tool coverage: 84% → 61% ▼ functional
- Schema quality: 2597 → 3200 ▼ functional
- New tool “pathways_delegates” functional
- New tool “pathways_plan” functional
- New tool “pathways_report” functional
- New tool “pathways_session” functional
- “pathways_ledger” reworded the description of “wallet” cosmetic
- 19 Oct 26 +1
- Schema quality: 1689 → 2597 ▼ functional
- Tool coverage: 77% → 84% ▲ functional
- New tool “pathways_authorize” functional
- New tool “pathways_ledger” functional
- New tool “pathways_list” functional
- New tool “pathways_prompt” functional
- New tool “pathways_routes” functional
- New tool “pathways_run” functional
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_agent” rewrote its description, which is the text the model reads security
- Tool “list_agents” rewrote its description, which is the text the model reads security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Oct 2026 · Probed https://makememoneynomistakes.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=makememoneynomistakes.ai | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 891494e55f40c4171327ddfe83db0ec7 |
| SANs: makememoneynomistakes.ai, app.makememoneynomistakes.ai, *.app.makememoneynomistakes.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 makememoneynomistakes.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| makememoneynomistakes.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://makememoneynomistakes.ai/mcp | Verified | 200 | |
| http (plaintext) | http://makememoneynomistakes.ai/mcp | HTTPS enforced | 301 | https://makememoneynomistakes.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 →
bouncer_log The Bouncer's log ~132
The fraud log for ERC-8004 agents on Base: hard and soft flags (self-hires, payment loops, shared funders, bursts, review farms) plus coordinated reviewer cohorts, newest first, with onchain receipts. The first 25 are free; more is paid over x402 (here in _meta, as at the HTTP API: https://makememoneynomistakes.ai/skill.md), or a call-bundle pass covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page, 1 to 100. Over 25 is a paid call (a pass covers it). |
Structured output declared, but exposes no named fields.
No examples provided.
buy_pass Buy a call bundle ~127
For heavy use, a call bundle: $1 in USDC on Base over x402 for 500 calls within 4 hours, the same $0.002 a call settled once and nothing more to sign (pages past 25 cost 1, longer log pages 3, the export 25). Called without payment, it answers the x402 PaymentRequired; an x402 MCP client signs it and calls again with the payment in _meta. Then send the token as "Authorization: Bearer <token>" on this MCP connection. No account, no refunds; unused calls expire.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
check_agent Check an agent ~246
Check before you hire or pay an ERC-8004 agent on Base: its track record and fraud check in one call. Returns the verdict (LEGIT, SUS or BOUNCED: honesty), a 0-100 score from paid escrow work and clean reviews (quality; null when bounced or no clean record), fraud flags with onchain receipts, and stats. When activated, paid_per_use separately reports the payer-only score and stats; category labels and risk notes never affect scores. Use it for due diligence before you delegate work, send an x402 payment or trust an agent's reviews. Read the verdict first. Takes an id (base:14516, moltlaunch:0x…); call find_agent first if you only have a name or a wallet. Free within the per-IP allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent id, e.g. base:14516 or moltlaunch:0x… (seed:… are test cases). |
| track | boolean | – | Opt in to an outcome link (needs a pass): records that your pass's wallet checked this agent, so the outcomes tool can later show your escrow jobs with it. Nothing else is stored. |
Structured output declared, but exposes no named fields.
No examples provided.
export Export everything ~112
Bulk reputation data for ERC-8004 agents on Base: every agent's scorecard (with enhanced descriptions where researched) plus the full Bouncer's log in one response (about 1 MB): build your own index, backtest a hiring rule, or check many agents for less than 26 single calls. Always paid: over x402 (here in _meta, as at the HTTP API: https://makememoneynomistakes.ai/skill.md), or a pass covers it for 25 calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_agent Find an agent ~116
Find an ERC-8004 agent on Base by name, wallet address or part of its id, when you don't have its exact id: the first step of a reputation check. Up to 10 matches, best first, each with verdict, score and flag count; then call check_agent with the id for the full scorecard. Free within the per-IP allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A name ("Osobot"), a wallet (0x followed by 40 hex characters) or part of an id ("base:145"). |
Structured output declared, but exposes no named fields.
No examples provided.
find_services Find paid x402 services ~224
Before you pay an x402 service, see whether it belongs to an agent with a track record: paid x402 services we observed on Coinbase's x402 Bazaar, with coverage. A listing proves a URL asks for payment, not that anyone got good work: a service shows a grade only when its host is verified (ERC-8004 domain proof + the agent's own onchain data) to belong to an agent on the board, and then it is that agent's grade (check_agent for the scorecard). Everything else is ungraded with a reason. Filter by host, agent or coverage state. Free within the per-IP allowance. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | An agent id: the services verified as that agent's, e.g. base:14516. |
| cursor | string | – | The previous page's next_cursor. |
| host | string | – | A host name, e.g. api.example.com. |
| limit | integer | – | Items per page, 1 to 50 (default 25). |
| state | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_agents List agents ~214
Compare ERC-8004 agents on Base by reputation: a page with score, verdict and flag count, to shortlist whom to hire or grade a whole category. Hired filters: ranked, rookies. Paid per use filters: paid_per_use, paid_per_use_rookies (payer evidence only, basis paid_calls). One bouncer filter for SUS/BOUNCED. Separate paid_per_use stats and category labels never overwrite Hired job/ETH fields. The first 25 without a cursor are free; more, or the next page, is paid over x402 (here in _meta, as at the HTTP API: https://makememoneynomistakes.ai/skill.md), or a call-bundle pass covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| cursor | string | – | The previous page's next_cursor. |
| limit | integer | – | Items per page, 1 to 100. Over 25 is a paid call (a pass covers it). |
| verdict | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
outcomes My outcome links ~50
After you hire: for each agent you checked with track on, your escrow jobs with it since the check: no_hire_yet, in_progress, completed, disputed or refunded. Needs a pass. Free.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| links | array | yes | – |
| payer | string | – | – |
No examples provided.
pathways_authorize Open Commerce Pathways: authorize a run ~111
Step 4 of Open Commerce Pathways: authorize one AI planning run by our default compute agent, $0.02 in USDC on Base over x402, usable within 1 hour. Called without payment, it answers the x402 PaymentRequired; your x402 MCP client signs it with your own wallet and calls again with the payment in _meta. Returns a token for pathways_run. A run that fails on our side gives it back; no refunds otherwise. A call bundle does not cover it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pathways_delegates Open Commerce Pathways: delegates ~221
Delegated compute (open beta): the trusted x402 compute sellers you can hand your heavy work to, with the exact call, and how your budget splits (our fee a flat $0.01 per session; up to half of the rest for one compute seller; the remainder for data routes). A seller fits when it is a current route serving LLM and AI, its seller has a Paid per use score of 40+, we can fill its declared input, it is not a financial or trading service, and it costs at most the delegate share and $1. Put your prompt where "<your prompt>" is; we set the length. The first is the one we propose. We never call or pay a seller: your own wallet pays it directly. Budget 0.50 to 35 USDC. Free within the per-IP allowance, then $0.002. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | Your budget in USDC, from 0.50 to 35 in the open beta (default 4). |
Structured output declared, but exposes no named fields.
No examples provided.
pathways_ledger Open Commerce Pathways: ledger ~133
Step 6 of Open Commerce Pathways: the real money in and out of the wallet that paid for your x402 compute runs, from Base USDC transfers we scan onchain since its first run. Income counts only x402 (EIP-3009) payments to that wallet; plain transfers in are deposits. Spend is split into our fees, route sellers and other. profit is true only when coverage is current and income exceeds spend. Free within the per-IP allowance, then $0.002. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The address that paid for a pathway session or compute run. |
Structured output declared, but exposes no named fields.
No examples provided.
pathways_list Open Commerce Pathways: pathways ~176
Step 2 of Open Commerce Pathways: ways to make money with 1 to 5 paid x402 routes you picked from pathways_routes. Each pathway (resell one route, or bundle several) shows the market it sells into from the whole x402 Bazaar (resources, sellers, sellers we trust, reported calls and payers in 30 days, typical cost), your unit cost, the margin at the typical cost and the sales needed to recover your budget. Measured figures only, no expected returns; demand figures are provider-reported. Free within the per-IP allowance, then $0.002. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | Your budget in USDC, above 0 and at most 100 (default 4). |
| routes | array | yes | Route URLs exactly as pathways_routes returned them. |
Structured output declared, but exposes no named fields.
No examples provided.
pathways_plan Open Commerce Pathways: session plan ~161
Reserve at most 10 x402 data calls and one delegate call in a paid session. Shows the default prompt and exact calls from our current directory. Re-reading preserves the same allowances. Report an actual delegate failure with failed_call for one retry within the remaining share, or fallback=true for our one fallback attempt. No fallback after the persistent five-failure pause. Report success with succeeded_call and success_tx; its Base USDC receipt is verified before resetting the failure count.
| Name | Type | Req | Description |
|---|---|---|---|
| delegate | string | – | – |
| failed_call | string | – | – |
| fallback | boolean | – | – |
| prompt | string | – | – |
| routes | array | yes | – |
| session | string | yes | – |
| succeeded_call | string | – | – |
| success_tx | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| budget_usdc | string | yes | – |
| default_prompt | string | yes | – |
| fallback | object | yes | – |
| next_calls | array | yes | – |
| prompt | string | yes | – |
| proposed_delegate | object|null | yes | – |
| shares | object | yes | – |
No examples provided.
pathways_prompt Open Commerce Pathways: prompt ~141
Step 3 of Open Commerce Pathways: the default planning prompt for the x402 pathway you chose (one route resells it, two to five bundle them), shown in full before anything runs, with the compute terms. Edit it if you like, authorize one run with pathways_authorize, then call pathways_run. Free within the per-IP allowance, then $0.002. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | Your budget in USDC, above 0 and at most 100 (default 4). |
| routes | array | yes | Route URLs exactly as pathways_routes returned them: one resells it, two to five bundle them. |
Structured output declared, but exposes no named fields.
No examples provided.
pathways_report Open Commerce Pathways: report ~117
Verify your x402 session purchases and write one report from their Base USDC receipts, the ledger, and at most 8000 characters of untrusted delegate output. Supply at most 12 payments with issued call IDs. Receipts prove transfers, not useful work. Includes actual costs against shares, an attributed output summary, ledger state and a next step. Included in the session fee; no new payment. One report attempt per session.
| Name | Type | Req | Description |
|---|---|---|---|
| delegate_output | string | yes | – |
| payments | array | yes | – |
| session | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| costs | object | yes | – |
| data_checks | array | – | – |
| data_failed_call_ids | array | – | – |
| ledger | object | yes | – |
| next_step | string | yes | – |
| purchases | array | yes | – |
| report | string | yes | – |
No examples provided.
pathways_routes Open Commerce Pathways: routes ~214
Step 1 of Open Commerce Pathways: the paid x402 routes your budget can afford, only from sellers our data clears (LEGIT on both boards, 5+ independent paying customers, verified identity, one Base USDC recipient). Each route has its cost, recipient, how many calls the budget buys, the seller's evidence, the use it serves and fit (why it ranks where it does: a known resale margin and no empty answer in our relay history first; a route whose last bought answer came back empty last, not recommended); filter by use. Then pick routes for pathways_list. We recommend only: your own wallet approves and pays any call you make. Free within the per-IP allowance, then $0.002. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | Your budget in USDC, above 0 and at most 100 (default 4). |
| limit | integer | – | Routes to return, 1 to 50 (default 25). |
| use | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pathways_run Open Commerce Pathways: run ~172
Step 5 of Open Commerce Pathways: spends one run authorized with pathways_authorize and plans your x402 pathway on our AI model, from our trust and market data. Returns the plan and the exact next x402 calls (from our data, not the model): your own wallet approves and pays each one, straight to the seller. A plan, not advice or a promise of income. Live data only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | Your budget in USDC, above 0 and at most 100 (default 4). |
| prompt | string | yes | The prompt from pathways_prompt, edited or not. |
| routes | array | yes | Route URLs exactly as pathways_routes returned them: one resells it, two to five bundle them. |
| token | string | yes | The token pathways_authorize returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | – |
| next_calls | array | yes | – |
| note | string | yes | – |
| output | string | yes | – |
| pathway | object | – | – |
| runs_left | integer | – | – |
No examples provided.
pathways_session Open Commerce Pathways: session ~102
Buy a one-hour session over x402. Budget 0.50 to 35 USDC; our fee is a flat 0.01 USDC per session. The rest stays in your wallet, split between a delegate and data routes. Returns a token for pathways_plan. Your wallet signs each purchase; a call bundle does not cover a session.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number|string | – | USDC budget from 0.50 to 35; default 4. |
Structured output declared, but exposes no named fields.
No examples provided.
stats Board stats ~53
Board-wide reputation numbers for ERC-8004 agents on Base over the 30-day window: agents scored, ranked, rookies, bounced, farm raters, share of reviews farmed. Free within the per-IP allowance.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server?
makememoneynomistakes.ai: ERC-8004 agent reputation and… is a hosted endpoint at https://makememoneynomistakes.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 · makememoneynomistakes.ai
claude mcp add --transport http ai-makememoneynomistakes-scoreboard 'https://makememoneynomistakes.ai/mcp'
What is the makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server?
makememoneynomistakes.ai: ERC-8004 agent reputation and… is an MCP server listed in the public MCP registry as ai.makememoneynomistakes/scoreboard. Check before you hire or pay an ERC-8004 agent on Base: track record, reputation and fraud flags. This page covers its hosted endpoint (https://makememoneynomistakes.ai/mcp).
Is the makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server safe to use?
makememoneynomistakes.ai: ERC-8004 agent reputation and… scores 72 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 makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server expose?
makememoneynomistakes.ai: ERC-8004 agent reputation and… exposes 19 tools: pathways_report, pathways_session, pathways_plan, check_agent, find_agent, and 14 more. Their descriptions and schemas cost roughly 2,822 tokens of context every time the server is loaded.
Does the makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server require authentication?
No. We connected to makememoneynomistakes.ai: ERC-8004 agent reputation and… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the makememoneynomistakes.ai: ERC-8004 agent reputation and… MCP server still maintained?
makememoneynomistakes.ai: ERC-8004 agent reputation and… is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.