AgentScore MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | The port the HTTP/SSE server should listen on (used for HTTP transport mode). | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getAgentScoreB | Returns current reputation score, history count and metadata URI. Accepts tokenId (number) OR agent address (0x...) |
| getAgentHistoryC | Returns array of past scores with timestamps (recent first) |
| listRegisteredAgentsB | List all agents (or single agent by owner address). Returns enriched data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: getAgentHistory retrieves historical data, getAgentScore provides current reputation metrics, and listRegisteredAgents enumerates agents with optional filtering. There is no overlap in functionality, and the descriptions clearly differentiate their roles.
The naming is mixed: getAgentHistory and getAgentScore follow a consistent verb_noun pattern, but listRegisteredAgents uses a different verb style ('list' vs. 'get'). While all names are readable, the inconsistency in verb choice reduces predictability.
With only 3 tools, the set feels thin for a server named 'AgentScore MCP Server', which suggests a broader scope for managing agent scores and data. While the tools cover basic retrieval and listing, the count may be insufficient for comprehensive operations like updating scores or managing registrations.
The tool surface is significantly incomplete for an agent scoring system. It only includes read operations (get and list), with no ability to create, update, or delete scores or agents. This leaves obvious gaps in CRUD coverage, likely causing agent failures in scenarios requiring data modification.