# Reported issues for MCPfinder - MCP Server Discovery

Pod holds 5 of 5 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to [MCPfinder - MCP Server Discovery](/mcp/mcpfinder-mcp-server-discovery).

## Most discussed

### Snapshot publication is frozen

The public snapshot manifest is **stale** (`age-exceeded`): the published snapshot is 18.8h old (threshold 18h, publishedAt 2026-09-21T22:14:05.717Z)

- `publishedAt`: `2026-09-21T22:14:05.717Z`
- age: `18.8` h (alarm threshold 18 h — three missed 6-hourly builds)
- checked by: https://github.com/mcpfinder/mcpfinder/actions/runs/35758239856

The previous complete snapshot is **still being served**; this is a
data stall, not an availability incident. Check whether the scheduled
build is still…

[Read the thread](https://github.com/mcpfinder/mcpfinder/issues/18) · 2026-09-22 · closed · external user · 5 comments

### `get_install_config` emits environment-variable *descriptions* as config *values*, discarding the `default` and `placeholder` fields present in the same object

**Versions:** `@mcpfinder/server` 1.1.0, `@mcpfinder/core` 1.1.0, Node v22.23.1, macOS 26.5.1, x86_64. Catalogue snapshot of 50,108 servers, last synced 2026-08-22.

**Context on the reporter:** I'm not a developer. I'm using MCPfinder while building a personal, fully local home assistant on my own machine, and I investigated this with the help of Claude Code. I found it while reviewing what `get_install_config` actually hands a user to paste.

## Summary

`get_install_config` builds the `env`…

[Read the thread](https://github.com/mcpfinder/mcpfinder/issues/10) · 2026-08-23 · closed · external user · 3 comments

### Snapshot publication has been frozen since Aug 20 by Glama pagination 404s

### Summary

The public snapshot manifest is still dated `2026-08-20T07:17:12.262Z`, while the scheduled `build-snapshot` workflow has failed repeatedly since then. The failures appear to be caused by a Glama pagination request returning 404, which trips the required-source quality gate and prevents publication even though the Official Registry sync succeeds.

### Evidence

Public manifest:

```text
https://mcpfinder.dev/api/v1/snapshot/manifest.json
publishedAt: 2026-08-20T07:17:12.262Z
```…

[Read the thread](https://github.com/mcpfinder/mcpfinder/issues/8) · 2026-08-23 · closed · external user · 2 comments

### Optional ASM value metadata under server.json _meta?

Hi — I’m working on Agent Service Manifest (ASM), a small MCP-compatible value metadata layer for service selection.

MCP Finder already discovers, evaluates, and installs MCP servers across sources like the Official Registry, Glama, and Smithery, so it seems like a good place to test whether optional value metadata would help server search and trust signals.

MCP already tells agents what a server can do. ASM adds optional structured metadata for what a service is worth before invocation:…

[Read the thread](https://github.com/mcpfinder/mcpfinder/issues/2) · 2026-05-08 · closed · external user · 2 comments

### Pilot/repro: indexed AssetFare remote is name-findable but not cross-chain quote-intent-findable

Disclosure: I maintain AssetFare. This is not a request for favorable ranking or promotion; I am offering a small discovery-quality fixture because MCPfinder already indexes the server.

Against `@mcpfinder/server@1.4.0` and the 2026-09-16 snapshot, `search_mcp_servers(query="assetfare")` finds the canonical Official+Glama record, and `get_install_config` marks its remote endpoint auto-installable with no secrets. But `cross-chain route quote`, `Solana Base swap quote`, and `bridge crypto…

[Read the thread](https://github.com/mcpfinder/mcpfinder/issues/17) · 2026-09-17 · open · external user · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/mcpfinder/mcpfinder/issues).