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/fieldcure/fieldcure-mcp-essentialsInstalling this writes the configuration, not the program: `dotnet` has to be on your PATH already, or the server will not start.
Wrote 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/fieldcure/fieldcure-mcp-essentials/essentials)<a href="https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-essentials/essentials"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-essentials/essentials/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/fieldcure/fieldcure-mcp-essentials/essentials"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-essentials/essentials.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
essentials 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
{
"essentials": {
"command": "dotnet",
"args": [
"run",
"--project",
"src/FieldCure.Mcp.Essentials",
"--",
"--search-engine",
"serpapi"
]
}
}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 · 13 lines scan A 80018cdd0bb3
essentials is an MCP server published in the GitHub repository fieldcure/fieldcure-mcp-essentials (0 stars, last pushed 5mo 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
orchestrator
MCP server "orchestrator" as configured in Byggarepop/dotnet-mcp-orchestrator. Launched with dotnet run --project C:/Users/sebas/Projects/MCP/McpOrchestrator/McpOrchestrator. Needs 1 environment variable to run.
dotnet-mcp-orchestrator
MCP server "dotnet-mcp-orchestrator" as configured in Byggarepop/dotnet-mcp-orchestrator. Launched with McpOrchestrator.
mcp-telegram
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.
itglue-mcp
MCP server "itglue-mcp" as configured in WYRE-AI/itglue-mcp. Runs in Docker (ghcr.io/wyre-ai/itglue-mcp:v1.17.2). Needs 6 environment variables to run.
apibase
MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo. Runs locally from the apibase-mcp-client npm package.