Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

The MCP server has no metrics

Aperta
  • Qualcosa non va?
#425 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@rupesh-kumar-sah ci sta già lavorando.

Dal 17/10/2026.

  • #439 di @sparkysolutions10-pixel — aperta
  • #446 di @rupesh-kumar-sah — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area:observability difficulty:easy help wanted points:100 Stellar Wave
Background

src/metrics.ts knows nothing about MCP. There is no count of tool calls, no
duration, no error breakdown — so the agent surface is entirely invisible on the
dashboard that covers every other part of the service.

Once L213 and L214 give agents something worth calling, "which tools are
actually used" becomes the question that decides what to build next, and there
will be no data to answer it.

What to build
  • A counter of tool calls by tool name and outcome. Tool names are a fixed,
    server-defined set, so this label is safely bounded — unlike the GraphQL
    operation names in #374.
  • A histogram of tool call duration by tool.
  • A counter of errors by the MCP_ERROR_CODES value, which is already a closed
    set and is exactly the right label domain.
  • Register on the existing registry so everything appears at /metrics.
Acceptance criteria
  • Tool calls are counted by name and outcome
  • Duration is recorded per tool
  • Errors are counted by error code
  • All labels come from closed sets
  • Metrics appear on the existing /metrics endpoint

Drips Wave · Complexity: Easy · 100 points

Repo: Divinity-Labs/Lens. The MCP server is src/mcp/server.ts
(BazaarMcpServer) with error codes in src/mcp/codes.ts. It is started by
npm run mcp:server → examples/mcp-server/run.ts, and there is an agent
example at examples/mcp-server/agent.ts. Tests are tests/mcp.test.ts.

Run the tests: npm test. The tests are vitest, not jest. A single file
is npx vitest run tests/mcp.test.ts.

Load test (prices) is already failing on main. Not your PR.

This surface signs with a real mainnet key. examples/mcp-server/run.ts
requires MCP_AGENT_SECRET_KEY_MAINNET and builds a signer for
stellar:pubnet. Anything you change here can move real money, so prefer
failing closed, and never log, echo or test with a real secret key.

Never elide an address, a contract id or a key in code, comments or
fixtures. A previous batch shortened a contract id and five contributors
invented plausible-looking ids to fill the gap. Write it in full or not at all.

An agent is the least able caller to notice a wrong answer. It will reason
over whatever it is handed, confidently. Prefer a structured error over a
best-effort result.

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

Lingua principale
TypeScript
Stelle
4
Fork
71
Merge medio
1g 6h
PR unite (30g)
58

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Divinity-Labs/Lens

Tutte le issue di Divinity-Labs/Lens

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.