ospec
mcp1.6.1Spec-driven, agentic workflow framework for AI coding agents. Turn a request into a verifiable goal loop — plan, act, verify — with durable specs and evidence in your repo. Works with Claude Code, Codex, Gemini, OpenCode, and plain CLI.
By clawplays | 13 findings | Scanned 10/15/2026 | tooltrust-scanner/v0.3.20 | 391
Repository health
Popularity and maintenance signals alongside the security grade.
391
current snapshot
26
current snapshot
3
public GitHub contributors
Aug 26, 2026
GitHub repository activity
Aug 26, 2026
2.1.0 - categorised doc bindings, coverage/bind/retire pipelines, and a generated docs map
2.1.0
Latest GitHub release
Stars trend
Daily star additions · githubarchive_bq · observed through Oct 3, 2026 · export updated Nov 1, 2026
Pull request activity
Weekly PR events · githubarchive_bq · observed through Oct 3, 2026 · export updated Nov 1, 2026
No observed PR events yet.
Data quality: observed_events. Charts show observed events, not a reconstructed historical total.
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (13)
gitwhy_search:tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
declared capabilities: filesystem access
gitwhy_getgitwhy_savegitwhy_statusdeclared capabilities: network access, filesystem access, database access
gitwhy_searchFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
gitwhy_getgitwhy_listgitwhy_post_prgitwhy_publishgitwhy_savegitwhy_searchgitwhy_statusgitwhy_syncFix: Review and remediate the identified issue.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y ospec"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)