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/timfurlong/msgraph-mcpWrote 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/timfurlong/msgraph-mcp/msgraph-mcp)<a href="https://agentmods.dev/mcp/timfurlong/msgraph-mcp/msgraph-mcp"><img src="https://agentmods.dev/badge/mcp/timfurlong/msgraph-mcp/msgraph-mcp/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/timfurlong/msgraph-mcp/msgraph-mcp"><img src="https://agentmods.dev/badge/mcp/timfurlong/msgraph-mcp/msgraph-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
msgraph-mcp 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
{
"msgraph-mcp": {
"command": "uvx",
"args": [
"msgraph-mcp-server"
],
"env": {
"MSGRAPH_MCP_CLIENT_ID": "",
"MSGRAPH_MCP_TENANT_ID": "",
"MSGRAPH_MCP_TOKEN_CACHE_PATH": ""
}
}
}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 c5ab664220e2
msgraph-mcp is an MCP server published in the GitHub repository timfurlong/msgraph-mcp (1 stars, last pushed 23d 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
outlook-mcp
MCP server for Microsoft Outlook via Microsoft Graph API. Runs locally from the outlook-graph-mcp Python package.
caldav-mcp
CalDAV calendar operations (list, create, update, delete events) as MCP tools. Runs locally from the caldav-mcp npm package. Needs 3 environment variables to run.
openclaw
Model Context Protocol (MCP) server for OpenClaw AI assistant integration. Runs locally from the openclaw-mcp npm package.
joplin-mcp
Model Context Protocol (MCP) server for Joplin note-taking application. Runs locally from the joplin-mcp Python package. Needs 2 environment variables to run.
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.
slack-mcp-server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. Runs locally from the @jtalk22/slack-mcp npm package. Needs 2 environment variables to run.