A
licenseA
qualityA
maintenanceEvidence checks and permission-scoped environment awareness for AI agents.
8
Apache 2.0
Noticer Receipt Maker for MCP
Related Servers
Alternatives to Noticer Receipt Maker for MCP
No user-submitted related servers found.
Related Servers
Consail MCPofficial
AlicenseNot gradedqualityBmaintenanceConnects agents to Consail over local stdio, providing read-only, allowlisted tools to inspect environments, catalogs, datasets, actions, and validate pipelines without exposing database credentials or secret APIs.Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables agents to audit GitHub Actions workflows for least-privilege problems and generate per-job hardened permissions plans through stdio MCP tools.0MIT
- AlicenseNot gradedqualityBmaintenanceExposes security scanning, code review, compliance checking, and release readiness as Model Context Protocol tools over stdio, enabling GitLab Duo agents or flows to invoke lifecycle checks.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local, read-only static inspection of Python/FastAPI, Docker, and GitHub Actions release evidence through a stdio interface, returning rule and instance findings without importing or executing target code.Apache 2.0
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
TDQS
A3.6/5.0
Scored across 10 tools
Disambiguation3/5
The receipt lifecycle tools (prepare, run, status, get_verified) are reasonably distinct once you follow the workflow. However, three separate onboarding tools (commercial_setup, enroll_commerce, initialize_local) plus commercial_account all have subtly overlapping 'get started' purposes that an agent could easily confuse. The dense descriptions help, but boundaries between setup/account/enroll remain fuzzy.
Naming Consistency3/5
All tools share the 'noticer_' prefix and snake_case, which is good. But verb conventions are mixed: some are verb_noun (prepare_receipt, get_verified_receipt, run_receipt), while others are noun phrases (commercial_setup, receipt_status, payment_challenge) with no action implied. The pattern isn't predictable enough to infer behavior from the name.
Tool Count4/5
Ten tools is well within the appropriate range for a commerce-plus-receipt verification lifecycle. Each stage (setup, enrollment, prepare, run, status, verify, payment) roughly earns its place, though a couple of onboarding tools could arguably be consolidated.
Completeness4/5
The surface covers the full lifecycle end to end: local setup, enrollment, account eligibility, receipt preparation, observation, polling, verification, payment challenge, and payment. No obvious dead ends for the core flow, though error-recovery and cancellation paths are only implied through descriptions rather than dedicated tools.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive