Report broken MCP entry: saurrx/mcp-test

[tensorblock-mcp-automation]

TensorBlock profile URL, server id, or project URL

https://github.com/saurrx/mcp-test

What is wrong?

• Dead link
• Duplicate entry
• Wrong category
• Incorrect install command
• Incorrect auth or transport metadata
• Stale project
• Security or safety concern
• Other

Details

GitHub API returned 404 for https://github.com/saurrx/mcp-test.

Indexed server id: github-saurrx-mcp-test-2584b5cd
Name: saurrx/mcp-test
Category: Infrastructure
Source docs: docs/infrastructure.md

A maintainer should verify whether the project moved, became private, or should be removed from the catalog.

Source or proof

https://github.com/saurrx/mcp-test

Generated by

TensorBlock MCP catalog health check.

[tensorblock-mcp-automation]

Thanks for reporting a broken MCP entry in #2713.
What happens next:

• We will verify the duplicate, dead link, stale metadata, wrong category, or safety concern.
• If this is a clear dead link and the URL still returns a dead status, automation can draft a cleanup PR against the matching docs/*.md entry.
• For duplicates, wrong categories, stale metadata, or safety reports, automation drafts an investigation spec PR for maintainer review.
• If there is a clear correction, a direct PR against the matching docs/*.md entry is welcome.
• Safety or security reports are routed with higher priority.
  Captured from the form:
• Entry: https://github.com/saurrx/mcp-test

Useful links:

• Contribution guide: https://github.com/TensorBlock/awesome-mcp-servers/blob/main/docs/index-alpha/contribution-guide.md
• Hosted MCP Index API: https://mcp-index.tensorblock.co
• TensorBlock Discord: https://discord.com/invite/Ej5NmeHFf2

If the index is useful for your project, starring the repo helps more MCP builders discover it.

[tensorblock-mcp-automation]

Created a cleanup PR for verified-dead entry https://github.com/saurrx/mcp-test: #2717

The automation rechecked https://github.com/saurrx/mcp-test and received HTTP 404, then removed the matching docs entry from docs/infrastructure.md.

Source issue: #2713