MCP Server List

Request TensorBlock MCP Index review

A community category directory that generates searchable server profiles and installation metadata after reviewed changes deploy.

Open a maintainer intake issue; catalog contribution remains separate. This action is separate from the qualifying submission minimum.

Guarded intake and deployed profile verificationSources checked

What to prepare

  • An active public source repository with accurate installation and authentication details.
  • A valid current intake category and no existing matching source or request.
  • Verified owner authority, service contribution identity and the reviewed issue template.

Follow the contribution into the hosted index

The maintained intake can produce a category contribution. MCP Server List keeps issue acceptance separate from merge and deployed profile verification. The index API must match the approved source identity and any known connection metadata before the canonical profile is credited as live.

Submission workflow

  1. Check current source and intake duplicates.
  2. Review the exact generated intake issue.
  3. Authorize its submission and follow the independently verified issue receipt.
  4. Confirm the linked merged contribution, category source and deployed public API profile separately.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • A duplicate or unusable project URL.
  • Missing metadata or unclear category routing.

Primary sources

Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.

← Compare all destinations