A public record of firecrawl-mcp-server's tool definitions over time

[GautamTalksDev]

Hi,

I've been building a public log of MCP tool definitions, because clients ask a user to approve a server once and then never re-check. If a description changes in a later release, nothing tells that user.

Here's the page for firecrawl-mcp-server: https://mcp-pin.gautamkhosla.com/servers/590e171c248baf58.html

What caught my eye is how much your descriptions are carrying. firecrawl_search is 1,177 characters and firecrawl_scrape is 1,110, roughly 10,000 across 25 tools. Those aren't labels, they're steering the model's behaviour. So a change to one is a behaviour change for every user who approved the old version, and their client never re-checks.

All 25 tools are fingerprinted now, so any future change shows up as a dated diff. If it's useful, there's a badge:

No ask beyond that. If you'd rather not be crawled, say so and it stops, no explanation needed: https://mcp-pin.gautamkhosla.com/about.html

And if this is useless to you, telling me why would be the most helpful reply I could get.

Gautam

[GautamTalksDev]

Follow-up: here's a 35-second walkthrough of what this looks like when it fires, including a real change it caught on day one.

https://youtu.be/uDFFiV10hLo

[GautamTalksDev]

The log caught your release. Between 2 Sep 19:12 and 3 Sep 07:06 UTC, 24 tools changed, one was removed (firecrawl_developer_search) and two added.

firecrawl_scrape went 1,110 → 5,420 chars, firecrawl_monitor_create 640 → 6,993, firecrawl_search 1,177 → 3,623.

Not a complaint, that's a normal release. The point is that anyone who approved your server yesterday is running against substantially different instructions today, and their client didn't mention it.

Full diff: https://mcp-pin.gautamkhosla.com/servers/590e171c248baf58.html

[GautamTalksDev]

Related to the diff above: there's now a GitHub Action that catches this in the PR that makes it, rather than after the fact.

yaml

• uses: GautamTalksDev/mcp-pin@v1
  with:
  command: node
  args: dist/index.js

The baseline is a file in your repo and it doesn't contact anything. Schema changes that leave the description untouched get flagged first.