_ registry / mcp streamable-http · checked 1h ago

com.epvotes/epvotes

https://epvotes.com

Registry code: 416171e89562c1df

api record

EP Votes answers questions about the European Parliament from stored official records: how MEPs and political groups voted in roll calls, what a dossier (legislative procedure) is and where it stands in Parliament, and what Parliament voted on a given day.

Typical path: search_parliament to find a dossier or MEP, then get_dossier, get_mep or get_vote. Use list_votes for "what did Parliament vote this week / on a day". Use compare_groups to compare political groups across recent votes.

endpoint
https://epvotes.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.epvotes/epvotes live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.epvotes/epvotes free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.epvotes/epvotes have?
6 tools: search_parliament, get_vote, get_mep, compare_groups, get_dossier, list_votes.
Is com.epvotes/epvotes safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
430ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_votes open 1h ago

    Use this when the user asks what the European Parliament voted on a sitting day, this week, between two dates or on a subject, e.g. "what did Parliament vote today" or "votes on Ukraine in October". Without arguments it returns the latest sitting day. Votes are grouped by agenda item; each item has its deciding (final) vote with result and totals and the vote ids for get_vote. Lists at most 40 items.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "End of a date range, YYYY-MM-DD (with from)."
        },
        "day": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "One sitting day, YYYY-MM-DD."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Start of a date range, YYYY-MM-DD (with to)."
        },
        "query": {
          "type": "string",
          "maxLength": 120,
          "description": "Keep only agenda items whose titles contain these words."
        },
        "this_week": {
          "type": "boolean",
          "description": "All votes of the current week."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • search_parliament unknown never probed

    Use this when you need to find a European Parliament dossier (legislative or non-legislative procedure), an MEP, a committee, a political group or an EP document by name, topic or reference, and you do not know its id yet. Returns up to 15 matching records with their ids and epvotes.com urls; pass an id to get_dossier or get_mep next. Matches words in titles and names (e.g. "digital euro", "Metsola", "ECON", "2023/0212(COD)"). Do not use it for votes of a day; use list_votes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "any",
            "dossier",
            "mep",
            "committee",
            "group",
            "document"
          ],
          "type": "string",
          "default": "any",
          "description": "Limit the search to one kind of record."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Words to match: a dossier title, procedure reference, MEP name, committee code or document number."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_vote unknown never probed

    Use this when you need the result of one European Parliament roll-call vote: totals, the split by political group and by country, the dossier it belongs to, and optionally how individual MEPs voted. Takes a vote id from list_votes, get_dossier or get_mep (or an epvotes.com/votes/<id> url). Set members to a group (e.g. "EPP", "S&D") or a country code (e.g. "DE", "FRA") to list those MEPs' votes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vote_id"
      ],
      "properties": {
        "members": {
          "type": "string",
          "maxLength": 40,
          "description": "Optional: list individual MEP votes for one political group or one country. \"all\" lists every MEP."
        },
        "vote_id": {
          "type": "string",
          "description": "The numeric vote id, e.g. \"198885\"."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_mep unknown never probed

    Use this when the user asks about one Member of the European Parliament: country, political group, committees, how often they vote with their group, where they broke with it, and their recent roll-call votes. Takes an MEP id or a name. Set topic to keep only votes whose titles contain those words (e.g. "digital euro", "Mercosur").

    mcp-tool

    {
      "type": "object",
      "required": [
        "mep"
      ],
      "properties": {
        "mep": {
          "type": "string",
          "maxLength": 120,
          "description": "The MEP id (e.g. \"124834\") or name (e.g. \"Martin Sonneborn\")."
        },
        "page": {
          "type": "integer",
          "default": 1,
          "maximum": 50,
          "minimum": 1,
          "description": "Page of votes, 25 per page, newest first."
        },
        "topic": {
          "type": "string",
          "maxLength": 120,
          "description": "Optional: only votes whose titles contain these words."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • compare_groups unknown 1h ago

    Use this when the user wants to compare how two or three European Parliament political groups voted across recent final votes on texts (amendments left out), e.g. "how often did EPP and S&D vote the same way". Groups: The Left, S&D, Greens/EFA, Renew, EPP, ECR, PfE, ESN.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groups"
      ],
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional end date, YYYY-MM-DD."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional start date, YYYY-MM-DD."
        },
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 50,
          "minimum": 1,
          "description": "Newest votes to compare."
        },
        "groups": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 3,
          "minItems": 2,
          "description": "Two or three group names, e.g. [\"EPP\", \"S&D\"]."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • get_dossier unknown 1h ago

    Use this when the user asks about one European Parliament dossier (procedure): what it is, its type, lead committee, rapporteurs, the steps so far in Parliament, its plenary votes, and the Legislative Observatory summary. Takes a procedure reference such as "2023/0212(COD)" or an id such as "2023-0212" (use search_parliament first if you only know the title).

    mcp-tool

    {
      "type": "object",
      "required": [
        "dossier"
      ],
      "properties": {
        "dossier": {
          "type": "string",
          "maxLength": 120,
          "description": "Procedure reference \"2023/0212(COD)\" or id \"2023-0212\"."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 416171e89562c1df.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/416171e89562c1df/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/416171e89562c1df/badge.svg)](https://brick.blue/agent/416171e89562c1df?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.