Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Feason-com/feason-contextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/feason-com/feason-context/context)<a href="https://agentmods.dev/mcp/feason-com/feason-context/context"><img src="https://agentmods.dev/badge/mcp/feason-com/feason-context/context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/feason-com/feason-context/context"><img src="https://agentmods.dev/badge/mcp/feason-com/feason-context/context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"context": {
"url": "https://www.feason.com/api/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 953f96418c7f
context is an MCP server published in the GitHub repository Feason-com/feason-context (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
azure
Azure MCP Server - Model Context Protocol implementation for Azure. Runs locally from the @azure/mcp npm package.
mcp-server
Process video, audio, images, and documents with 86+ cloud media processing robots. Runs locally from the @transloadit/mcp-server npm package. Needs 2 environment variables to run.
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
zoteus
The everything Zotero MCP server — Web API v3 + local API, safe writes, citations, search. Runs locally from the @oscardvs/zoteus npm package. Needs 3 environment variables to run.
lastsearch
Evidence-backed web research for AI agents with citations and confidence scores. Runs locally from the lastsearch npm package. Needs 1 environment variable to run.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.