kapoost-humanmcp
mcpsmitheryPersonal MCP server for humans who create. 39 tools: content publishing, Ed25519 signatures, license control, artworks with provenance, async Q&A, listings, federation. Your content, your rules.
By Smithery | 66 findings | Scanned 7/28/2026 | tooltrust-scanner/v0.3.19
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 (66)
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
request_accesssearch_contentrequest_licenseleave_messagequery_vaultrememberlist_provenancelist_peersannounce_peerupsert_skillsubscribe_listingsFix: 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
get_author_profileadd_provenancedelete_skilldelete_personadeclared capabilities: network access
request_accessrequest_licenseleave_messagequery_vaultlist_peersannounce_peerdeclared capabilities: network access, database access
search_contentdeclared capabilities: HTTP requests
rememberlist_provenanceupsert_skilldeclared capabilities: network access, HTTP requests
subscribe_listingsFix: 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.
get_author_profilelist_contentread_contentrequest_accesssubmit_answersearch_contentlist_blobsread_blobverify_contentget_certificateupgrade_timestamprequest_licenseleave_commentleave_messageask_humanget_answerbootstrap_sessionquery_vaultlist_vaultrememberrecalllist_provenanceadd_provenanceabout_humanmcplist_peersannounce_peerlist_skillsget_skillupsert_skilldelete_skilllist_personasget_personaupsert_personadelete_personalist_listingsread_listingrespond_to_listingsubscribe_listingsunsubscribe_listingsFix: Review and remediate the identified issue.
unsubscribe_listings:input parameter "token" accepts a credential (informational; not evidence of insecure handling)
Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.
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 kapoost-humanmcp"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)