
Perch Data
io.github.101NUTSPublished by GitHub account 101NUTSv1.0.0Updated Nov 2, 2026
Six Apify actors: prediction-market weather data, tennis odds, Nashville permits, kitchen takeoffs.
Overview
A retired Apify-hosted MCP listing that once exposed six data actors (weather prediction markets, tennis odds, Nashville permits, kitchen takeoffs); it no…
- What you can do
- No tools are listed and the server is retired, so there is nothing to call.
- The README states the listing was retired on 2026-09-21 and no longer serves data.
- The six Apify actors it pointed at are being unpublished, and the two prediction-market weather actors (Kalshi and Polymarket) were retired at the source and return nothing.
- The repository is archived and kept only as a record.
- When to use it
- Not applicable: the provider has closed and the README asks that this entry be removed from listings and indexes. Do not add it to a new setup; look for an actively maintained alternative instead.
- Requirements
- None that would help: the README says there is nothing to install or connect to any more, and the underlying actors are being unpublished or already return nothing.
Installation
In SourceWeft
- Open Perch Data in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.101NUTS%2Fperch-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"perch-data": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,get-actor-output,perchpermits/kalshi-weather-markets-nws,perchpermits/polymarket-weather-markets-stations,perchpermits/tennis-matches-odds-form,perchpermits/nashville-building-permits,perchpermits/kitchen-floor-plan-takeoff,perchpermits/apify-store-trends"
}
}
}README
Perch Data MCP — retired
This listing was retired on 2026-09-21 and no longer serves data.
Perch Data has closed. The six Apify actors this listing pointed at are being unpublished, and the two prediction-market actors (Kalshi and Polymarket weather) were retired at the source: they now exit with a retirement message and return nothing. There is nothing to install or connect to here any more.
If you listed or indexed this server (io.github.101NUTS/perch-data,
perchdata/perch-data), please remove the entry.
This repository is archived and kept only as a record.
License: MIT
Source: README.md at commit d14fb45
Tools
0Version history
1- v1.0.0LatestSep 20, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts