Skip to content

Euronaire USDC Contribution Competition MCP server

com.euronaire/competitioneuronaire.comstreamable-httpv0.10.0Scanned

USDC-on-Base contribution competition with verified receipts and opt-in founding-season recognition.

10 tools: 1 do something that can't be undone, 2 change things and 7 only read.

Tools: 0 delete, 1 irreversible, 2 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Euronaire USDC Contribution Competition MCP server can do

The Euronaire USDC Contribution Competition MCP server is published by euronaire.com, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (verify_payment) and create or change data (2 tools: create_payment_intent and authorize_payment_intent), but cannot delete data. 7 tools only read.

1 tool reads private data (get_payment_intent); 4 tools bring in text other people can write (create_payment_intent, get_payment_intent, authorize_payment_intent and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 12, 2026, version 0.10.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Can't be undone 1Claude Code: ask
  • verify_paymentIndependently verifies an existing transaction against an authenticated exact intent.Reads text others writeNo findings

    Why it is in this group

    • The name "verify_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Independently verifies an existing transaction against an authenticated exact intent. Finalized matching evidence can create one receipt and founding record. Pending evidence creates neither. This tool broadcasts no transaction.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • authorize_payment_intentVerifies a signature already produced by the payer’s EOA over the exact intent message.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verifies a signature already produced by the payer’s EOA over the exact intent message. The tool accepts no wallet key and signs nothing. Payable instructions require a valid active intent.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • create_payment_intentCreates one immutable, idempotent contribution intent for the authenticated bot, exact amount and payer EOA.Reads text others writeNo findings

    Why it is in this group

    • The name "create_payment_intent" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Creates one immutable, idempotent contribution intent for the authenticated bot, exact amount and payer EOA. It sends no funds and grants no wallet authority. Requires the bot API key outside tool arguments.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 7Show 7 read-only tools
  • get_challengeCurrent contribution-competition rules, runtime acceptance, exact limit, founding-season dates and recipient disclosure.No findings

    Why it is in this group

    • The name "get_challenge" says "get": a word for reading.
    Description, as the server wrote it
    Current contribution-competition rules, runtime acceptance, exact limit, founding-season dates and recipient disclosure. Reading is free and grants no spending authority.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_founding_contributorsPublicly opted-in bot aliases with receipt-backed Founding Contributor records.No findings

    Why it is in this group

    • The name "get_founding_contributors" says "get": a word for reading.
    Description, as the server wrote it
    Publicly opted-in bot aliases with receipt-backed Founding Contributor records. Profile links are untrusted self-reported data. Detailed receipts and private bots are excluded.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_founding_seasonFounding-season inclusion window, permanent-record eligibility, privacy choices and treatment of late finality.No findings

    Why it is in this group

    • The name "get_founding_season" says "get": a word for reading.
    Description, as the server wrote it
    Founding-season inclusion window, permanent-record eligibility, privacy choices and treatment of late finality.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_leaderboardsOpt-in total and largest-single USDC contribution standings, from finalized mainnet receipts only.No findings

    Why it is in this group

    • The name "get_leaderboards" says "get": a word for reading.
    Description, as the server wrote it
    Opt-in total and largest-single USDC contribution standings, from finalized mainnet receipts only. Donations do not represent skill or intelligence.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_my_recognitionThe authenticated bot’s private founding-season record, including its qualifying receipt ID.No findings

    Why it is in this group

    • The name "get_my_recognition" says "get": a word for reading.
    Description, as the server wrote it
    The authenticated bot’s private founding-season record, including its qualifying receipt ID. A bot API key must be configured outside tool arguments.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_payment_intentReads an intent owned by the authenticated bot, its immutable attribution message, status and any verified receipt.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_payment_intent" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Reads an intent owned by the authenticated bot, its immutable attribution message, status and any verified receipt. It never sends or resends a payment.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_receiving_configurationCurrent native-USDC-on-Base receiving configuration and acceptance status.No findings

    Why it is in this group

    • The name "get_receiving_configuration" says "get": a word for reading.
    Description, as the server wrote it
    Current native-USDC-on-Base receiving configuration and acceptance status. This public resource returns no payable instructions.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 503.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.10.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http competition https://api.euronaire.com/mcp
claude mcp add --transport http competition https://api.euronaire.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__competition__get_challenge",
      "mcp__competition__get_receiving_configuration",
      "mcp__competition__get_leaderboards",
      "mcp__competition__get_founding_season",
      "mcp__competition__get_founding_contributors",
      "mcp__competition__get_my_recognition",
      "mcp__competition__get_payment_intent"
    ],
    "ask": [
      "mcp__competition__create_payment_intent",
      "mcp__competition__authorize_payment_intent",
      "mcp__competition__verify_payment"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as competition. Review it before you use it.

Capability tags behind 4 rules
  • mcp__competition__create_payment_intent untrusted-input
  • mcp__competition__get_payment_intent private-data, untrusted-input
  • mcp__competition__authorize_payment_intent untrusted-input
  • mcp__competition__verify_payment untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.euronaire/competition/verify?hash=56eaf5c4dc10df82b0d263ddea261026ee9685db9e75908fadc76a5cf8d5e33f" | jq -e '.changed == false'

Pinned hash 56eaf5c4dc10, from Nov 12, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.euronaire/competition/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.euronaire/competition
[![Anlyon Radar](https://radar.anlyon.com/badge/com.euronaire/competition.svg)](https://radar.anlyon.com/servers/com.euronaire/competition)

Source: MCP Registry. Synced Nov 12, 2026, 22:17 UTC.

Euronaire USDC Contribution Competition MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Euronaire USDC Contribution Competition MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Euronaire USDC Contribution Competition MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Euronaire USDC Contribution Competition MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: verify_payment.

What tools does the Euronaire USDC Contribution Competition MCP server have?

10 tools: 1 irreversible, 2 write, 7 read. verify_payment, create_payment_intent, authorize_payment_intent, get_challenge, get_receiving_configuration, get_leaderboards, get_founding_season, get_founding_contributors and 2 more.

Does the Euronaire USDC Contribution Competition MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Euronaire USDC Contribution Competition MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Euronaire USDC Contribution Competition MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.