agent-card-starter
Related Servers
Alternatives to agent-card-starter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for German Electronic Invoicing (ZUGFeRD 2.x / XRechnung 3.x). Provides tools to validate, generate, parse, and convert invoices compliant with EN 16931 and KoSIT.5046 PyPI2Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for DACH e-invoicing. Create XRechnung (UBL) and ZUGFeRD 2.3 (Factur-X CII) invoices, validate against EN 16931 rules, extract data from XML, and convert between UBL, CII and JSON formats.661 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for German public procurement data (OCDS). Semantic search, tender matching, and company profiles — all from your local LLM105MIT
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for Spanish Electronic Invoicing. Provides tools to generate, validate, and submit invoices across VERI\*FACTU, Facturae/FACe, SII, TicketBAI, and Crea y Crece B2B.2036 PyPI3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.MIT
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for French Electronic Invoicing (NF XP Z12-013). Provide tools to validate, generate, and explore API specifications for PDP/OD interoperability.34Apache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists available services, the other creates an inquiry. There is no overlap or ambiguity in selecting between them.
Both names are in German and use snake_case, but they follow different conventions: 'leistungen' is a bare noun while 'anfrage_anlegen' is a verb_noun construction. The mixed style is readable but not predictable.
Two tools is on the thin side for a functional server, even a starter one. The set is not over-scoped, but it feels minimal and close to being too sparse.
The surface lacks basic lifecycle coverage: there is no way to retrieve service details, and the inquiry creation explicitly stores nothing. No update, delete, or persistence operations exist, creating significant dead ends.