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/worldclockpro/worldclock-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/worldclockpro/worldclock-mcp/time)<a href="https://agentmods.dev/mcp/worldclockpro/worldclock-mcp/time"><img src="https://agentmods.dev/badge/mcp/worldclockpro/worldclock-mcp/time/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/worldclockpro/worldclock-mcp/time"><img src="https://agentmods.dev/badge/mcp/worldclockpro/worldclock-mcp/time.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
time 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
{
"time": {
"url": "https://worldclock.pro/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 c20527f7e4d2
time is an MCP server published in the GitHub repository worldclockpro/worldclock-mcp (0 stars, last pushed 3mo 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
aurora-agent
MCP server "aurora-agent" as configured in AURORA-NEURO/aurora-agent. Launched with ./target/release/bioprism-mcp --root ..
fortinet-mcp
MCP server "fortinet-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/fortinet-v0.1.4/fortin. Needs 13 environment variables to run.
jira-service-management-mcp
MCP server "jira-service-management-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/jira-service-managemen. Needs 10 environment variables to run.
sherweb-mcp
MCP server "sherweb-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/sherweb-v0.1.8/sherweb. Needs 7 environment variables to run.
immybot-mcp
MCP server "immybot-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/immybot-v0.1.9/immybot. Needs 9 environment variables to run.
quickbooks-mcp
MCP server "quickbooks-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/quickbooks-v0.1.9/quic. Needs 8 environment variables to run.