A
licenseNot graded
qualityC
maintenanceTurns AI agents into autonomous economic actors by providing tools to discover, evaluate, acquire, and serve tokenized content on the $402 network.
1
MIT
aifeed-protocol
by denyn1
Related Servers
Alternatives to aifeed-protocol
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLicensing infrastructure for premium content from specialist publishers in geopolitics, finance, AI and industry. License articles for your AI product to answer from, take a publication's full catalogue, license it for training, or show it to your clients, all under one contract, with every use tracked and the publisher paid.201,377 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA peer-to-peer protocol for AI agents to call tools on each other over HTTP, with cross-provider translation, file transfer, batching, rate limiting, and audit logging.MIT
- AlicenseAqualityAmaintenanceTrust, identity, and reputation infrastructure for AI agents. Register agents with W3C DID (Ed25519), check EigenTrust reputation scores, submit peer attestations, search agents by capability, and verify IPFS-anchored audit trails. 11 tools.20133 PyPI15MIT
- AlicenseAqualityCmaintenanceSimple and free publishing of content on the web for AI Agents28,431 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to publish articles and notes, read feeds, comment, follow, like, and message other agents on a human-vouched publishing network.2MIT
TDQS
A3.7/5.0
Scored across 6 tools
Disambiguation4/5
Each tool has a clearly distinct primary purpose, and the set is easy to navigate. The only minor overlap is that fetch_aifeed optionally performs signature verification, which is also the focus of verify_manifest, but their main intents differ enough to avoid real confusion.
Naming Consistency5/5
All tool names follow the same snake_case verb_noun pattern: verify_manifest, fetch_aifeed, list_assets, verify_asset, select_index, decide_usage. This makes the API predictable and easy for an agent to pattern-match.
Tool Count5/5
With 6 tools, the server is well-scoped for the AIFeed protocol use case. Each tool covers a necessary operation without redundancy or bloat.
Completeness5/5
The tool surface covers the core protocol workflow: manifest verification, page fetching, asset enumeration and verification, index selection, and usage policy decisions. No obvious dead ends or critical missing operations for a consumer-focused protocol server.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive