io.github.rashidazarang/airtable-mcp
io.github.rashidazarang/airtable-mcp
Is the io.github.rashidazarang/airtable-mcp MCP server down? It gave no valid answer in the probe of 2026-11-19: crashed on start. One failed probe is not an outage.
Runs locally: Airtable records, schema, comments, upserts, base/table allow-lists and PII masking
crashed on start no valid answer since 2026-11-19 · probed 2026-11-20 · unchanged since 2026-11-19
MCP error -32000: Connection closed
at wrapModuleLoad (node:internal/modules/cjs/loader:254:19) {
code: 'GovernanceError',
context: {}
}- Run it
- npx -y @rashidazarang/airtable-mcp@5.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/rashidazarang/airtable-mcp
- Website
- https://www.airtablemcp.com/
- Registry
- active, updated 2026-11-19 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.raportagent/raportagent-mcp · alive
- io.github.rapozoantonio/memorykit · crashed on start
- io.github.raresv/cardora-business-assistant · not probed
- io.github.rascal-3/chainanalyzer-mcp · alive
- rasterly io.github.rasterly-dev/rasterly-mcp · alive
- io.github.ratamaha-git/n8n-mcp · alive
- io.github.raulkivi/agent-cost-analyzer · alive
- io.github.raullenchai/vnsh · alive
Servers that mention airtable.
- ai.waystation/airtable · paid (402)
- ai.waystation/mcp · paid (402)
- com.airtable/mcp · needs auth
- Airtable io.github.pipeworx-io/airtable · alive
- Airtable io.github.domdomegg/airtable-mcp-server · alive
- com.mcparmory/airtable · alive
- Airtable User MCP io.github.Automations-Project/airtable-user-mcp · alive
- Airtable MCP by InsightfulPipe com.insightfulpipe/airtable · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-19. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.