GitHub
MCP Servers
Repos, issues, PRs, code search
Read/write local files
API key
Not required
HTTPS
Not supported
Browser calls
Unconfirmed
Status
Not yet checked
A starting template for Filesystem. Replace ENDPOINT with the path from the official documentation, which we link above rather than guess at.
# No authentication required.
curl -s "https://github.com/ENDPOINT" \
-H "Accept: application/json"This API is served over plain HTTP. Browsers block HTTP requests made from an HTTPS page, so you will need a server-side call.
Aggregated from one public source (public-apis), then normalised and checked by us.
Report an issue with this listing ↗MCP Servers
Repos, issues, PRs, code search
MCP Servers
IP geolocation, threat and timezone lookups for agents
Answered from what our own scheduled checks found, not from the provider's marketing.
Filesystem is listed in our free catalogue and required no credential when we called it. It needs no authentication at all, so you can send a request without signing up. Free tiers can still carry rate limits or non-commercial terms, so check the provider's own terms before shipping.
No. We called Filesystem on our last run with no key, no token and no Authorization header, and it responded. That is what puts it in our no-key collection.
We could not confirm CORS support for Filesystem. Test it from a browser before relying on it client-side; if the request succeeds in curl but fails in the console, CORS is the reason.
No. Filesystem was only reachable over plain HTTP when we checked. Browsers block HTTP requests made from an HTTPS page, so this will fail in production unless you call it from a server instead.