mcp server
Foundry/API
Bounded tools for rendering, extraction, RAG, enrichment, local discovery and review analysis.
Description as published by the maintainer. Source
- version 0.1.1
- active
- data extraction
- retrieval
active — Most recent push to the repository was 2026-07-22. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-22 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
The Neural Ledger Intelligence
— last commit 2026-08-01, shares n8n, pipedream
Read-only global event and evidence intelligence with entities, assets, and impact paths.
-
Perfex CRM
— last commit 2026-08-04, shares n8n
Read and write a self-hosted Perfex CRM from an AI agent: 148 permission-filtered tools.
-
Skill of Skills
— last commit 2026-08-06, shares n8n
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers.
-
n8n MCP Community
— last commit 2026-08-05, shares n8n
A security-focused MCP server for self-hosted n8n Community Edition.
-
ai.klavis/strata
— last commit 2026-06-01, shares api
MCP server for progressive tool usage at any scale (see https://klavis.ai)
-
ai.pullpush/pullpush-mcp
— last commit 2026-07-30, shares api
Connect any two APIs and keep them in sync — 45 MCP tools with shadow previews and diagnostics.
-
ai.smithery/yuna0x0-anilist-mcp
— last commit 2026-07-13, shares api
Access and interact with anime and manga data seamlessly. Retrieve detailed information about your…
-
ai.smithery/yuna0x0-hackmd-mcp
— last commit 2026-07-13, shares api
Interact with your HackMD notes and teams seamlessly. Manage your notes, view reading history, and…
-
Amazon Trends API
— last commit 2026-08-03, shares api
Amazon product search volume and best-seller trends. Free key at trendsapi.ai
-
App Store Trends API
— last commit 2026-08-03, shares api
App downloads and chart ranking trends for iOS and Android. Free key at trendsapi.ai
These share tags the maintainers applied themselves, such as n8n, pipedream, api. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: api, developer-tools, mcp, n8n, pipedream, workflow-automation.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab