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/Intersect-Collaborations-LLC/research-workflow-assistantInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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/intersect-collaborations-llc/research-workflow-assistant/project-tracker)<a href="https://agentmods.dev/mcp/intersect-collaborations-llc/research-workflow-assistant/project-tracker"><img src="https://agentmods.dev/badge/mcp/intersect-collaborations-llc/research-workflow-assistant/project-tracker/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/intersect-collaborations-llc/research-workflow-assistant/project-tracker"><img src="https://agentmods.dev/badge/mcp/intersect-collaborations-llc/research-workflow-assistant/project-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-tracker 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 5d 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
{
"project-tracker": {
"type": "stdio",
"command": "${workspaceFolder}/.venv/Scripts/python",
"args": [
"-m",
"project_tracker"
],
"cwd": "${workspaceFolder}/mcp-servers/project-tracker/src",
"env": {
"PROJECT_DIR": "${workspaceFolder}",
"PROJECTS_ROOT": "${env:PROJECTS_ROOT}"
}
}
}What else mcp.json configures
This page is one entry in a file that holds 12. Installing the file brings all of them; each is measured and scanned on its own page.
- MCP server bibliography-manager A not measured
- MCP server chat-exporter A not measured
- MCP server crossref A not measured
- MCP server europe-pmc A not measured
- MCP server google-workspace A not measured
- MCP server openalex A not measured
- MCP server prisma-tracker A not measured
- MCP server pubmed A not measured
- MCP server semantic-scholar A not measured
- MCP server zotero A not measured
- MCP server zotero-local A not measured
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.
- 5d ago First seen · 15 lines scan A 2deb7b21fbb4
project-tracker is an MCP server published in the GitHub repository Intersect-Collaborations-LLC/research-workflow-assistant (26 stars, last pushed 5d 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-09-24.
Other mcp servers, from other repositories
mcp-server
Hosted OAuth MCP at https://www.taskade.com/mcp, or local @taskade/mcp-server. Runs locally from the @taskade/mcp-server npm package. Needs 1 environment variable to run.
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
find-research-papers-mcp
Search open-source research papers across arXiv, OpenAlex, Crossref, PubMed, Semantic Scholar. Runs locally from the find-research-papers-mcp npm package. Needs 1 environment variable to run.
p4plan-mcp
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API. Runs locally from the @perforce/p4plan-mcp npm package. Needs 3 environment variables to run.
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously. Runs locally from the @cyanheads/shift-mcp-server npm package. Needs 1 environment variable to run.
rootly-mcp
MCP server "rootly-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/rootly-v0.1.3/rootly-m. Needs 3 environment variables to run.