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.

Madrid Events

NPM · @PIPEWORX/MCP-MADRID-EVENTS · 2 COMPONENTS

Madrid Events MCP.

−2 this week 78 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
  • Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-madrid-events). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 216 tokens (~216/item across 1 items; 1 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 Management23
  • Stability observed for 7 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
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.

  • 5 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 4 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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 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.

  • 29 Oct 26 80

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-madrid-events@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-madrid-events
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-madrid-events/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649765070
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ac8c0ef18cd30bd2402af18d03a7d9497d04dade65c8feb563e20f9448e2893a1e0784c8d2f4a55ba536343fb71efbf84131dc8de9e74b6b616506882

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~163 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
events ~163

Find cultural events & activities in Madrid, Spain (next ~100 days). Filter by keyword, free admission, and date window. Returns events with venue, address, geo, audience and price. Content is in Spanish.

NameTypeReqDescription
free_onlyboolean–If true, only free events.
fromstring–Include events on/after this date YYYY-MM-DD (default: today).
limitnumber–Max events (1-50, default 20).
offsetnumber–Pagination offset (default 0).
querystring–Keyword over title, description and venue, e.g. "música", "exposición", "teatro".
tostring–Include events starting on/before this date YYYY-MM-DD.

No output schema declared.

No examples provided.

Install

How do I install the Madrid Events MCP server?

Madrid Events runs locally as an npm package, launched with npx -y @pipeworx/mcp-madrid-events. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-madrid-events

# add to Claude Code
claude mcp add pipeworx-io-madrid-events -- npx -y @pipeworx/mcp-madrid-events
Common questions

What is the Madrid Events MCP server?

Madrid Events is an MCP server listed in the public MCP registry as io.github.pipeworx-io/madrid-events. Madrid Events MCP. This page covers its npm package (@pipeworx/mcp-madrid-events).

Is the Madrid Events MCP server safe to use?

Madrid Events scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Madrid Events MCP server expose?

Madrid Events exposes 1 tool: events. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.

Is the Madrid Events MCP server still maintained?

Madrid Events is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Madrid Events MCP server under?

Madrid Events declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.