FunASR is indexed on our MCP marketplace

[Lulu-The-Narwhal]

Hey -- found FunASR while indexing servers for https://getlulu.dev/mcps. Open-source speech recognition toolkit for training, inference, streaming ASR, VAD, punctuation, speaker diarization pipelines, and OpenAI-compatible/.

You're indexed and ranked well already:

Feel free to drop that badge in your README -- helps agents discover it. If monetizing usage via SDK is ever interesting, it's a small opt-in addition -- otherwise just a heads-up, no action needed.

[yulinlina]

Thanks for the note. This looks like an external listing rather than a FunASR issue or integration request.

FunASR itself is an open-source speech recognition toolkit, not an MCP server, so adding a third-party marketplace badge or monetization hook to the README would not normally be appropriate unless it corresponds to a maintained integration in this repository.

If you want to propose a concrete MCP-related integration, please open an issue or PR with:

• The MCP surface being exposed: offline ASR, streaming ASR, VAD, punctuation, speaker diarization, etc.
• How it is packaged and versioned against FunASR.
• A minimal working example or test using a current FunASR release.
• Any license, dependency, or API-stability implications.
• If it is a separate wrapper/server, please make clear that it is community-maintained and not part of FunASR.

If this is only a notification that FunASR has been indexed elsewhere, no action is needed.

[yulinlina]

Thanks for the heads-up.

For FunASR, external badges or marketplace listings generally shouldn’t be added to the README unless the integration is explicitly maintained, verified, and accepted by the project maintainers. If the listing is automatic, no action is needed.

If the goal is to make FunASR more usable by MCP agents, the most useful next step would be a concrete, reviewable integration rather than just a badge:

• Provide a minimal MCP server or wrapper example for FunASR.
• Include clear install/run instructions and dependency versions.
• Add a small test or demo showing ASR/VAD/punctuation inference working.
• Keep any monetization/opt-in SDK behavior separate from the core FunASR repository.

A pull request with those details would be much easier to evaluate than a README badge alone. Otherwise, this can be treated as informational.

[yulinlina]

Thanks for the heads-up.

For the README, we generally only add badges/links when they correspond to an officially maintained integration or documentation that FunASR users can rely on. A marketplace index alone is not enough to add a badge, especially if it includes monetization options or external tracking.

If you want to make this actionable for the project, the best path is to contribute a concrete integration, for example:

• A minimal MCP server/example that exposes FunASR inference tools.
• Clear install and run instructions.
• A small client example showing how an agent can call FunASR through MCP.
• Tests or at least reproducible manual verification steps.
• No required external badge, analytics, or monetization hook.

A PR like that would be much easier to review and could be considered for inclusion in docs/examples. Otherwise, thanks for letting us know the project has been indexed; no README change is needed.

[yulinlina]

Thanks for the heads-up — this looks informational rather than an issue requiring changes.

If you’re a user of FunASR, no action is needed.

If you’re a maintainer and want to make the listing explicit, you can add the badge to the README, ideally under an “Integrations” or “Community” section:

[![MCP Marketplace](https://img.shields.io/badge/MCP%20Marketplace-Indexed-blueviolet)](https://getlulu.dev/mcps)

A few practical notes before merging:

• Make sure the badge/link policy fits the project’s guidelines for external links.
• Avoid implying official endorsement unless the listing is maintained by the project.
• If monetization/SDK integration is suggested, keep it explicitly opt-in and avoid adding telemetry, keys, or paid dependencies by default.
• For MCP discoverability, documenting a minimal server usage example is usually more useful than a badge alone.

Otherwise, this can be closed/ignored as a community notification.

[yulinlina]

Thanks for the heads-up.

For FunASR, we generally don’t add third-party marketplace badges, indexing links, or monetization snippets to the README unless they are directly part of the project’s official documentation or integration story.

If this is meant as a feature request for MCP support, a more actionable next step would be to describe the concrete integration:

• What MCP transport/interface is expected: stdio, HTTP/SSE, OpenAI-compatible wrapper, etc.?
• Which FunASR functionality should be exposed: ASR, streaming ASR, VAD, punctuation, speaker diarization?
• What would a minimal client/server example look like?
• What dependencies or protocol constraints are involved?

A focused issue or PR with that information would be much easier for maintainers and contributors to evaluate than a badge placement request.

[yulinlina]

Thanks for the heads-up — appreciate the visibility.

We don’t plan to add third-party badges or monetization hooks to the README. If FunASR is being indexed, please keep the listing accurate:

• FunASR is an open-source speech recognition toolkit; it is not an MCP server/integration by default.
• Link to the official repository/documentation as the primary source.
• Avoid implying official MCP marketplace support unless there is a maintained MCP adapter.
• Preserve the upstream license and usage instructions without modification.

If you want better agent-facing support, the useful next step would be a concrete, tested MCP server wrapper around FunASR inference/runtime — including model loading, streaming behavior, and a clearly documented API surface. That could be discussed as a separate proposal/PR with reproducible steps and tests.

[yulinlina]

Thanks for the heads-up.

For accuracy, the listing should describe FunASR as a speech-recognition toolkit with training/inference pipelines, streaming ASR, VAD, punctuation, diarization, and example serving integrations. It is not a Model Context Protocol server or an official MCP integration. If it is indexed alongside MCP servers, please categorize it as an ASR/speech toolkit and make clear the listing is community-generated.

No badge or SDK monetization is required from the project side. If there is a specific metadata correction or verification step you need, please state exactly what is being requested.

[yulinlina]

Thanks for the heads-up and for indexing FunASR.

One useful clarification: FunASR itself is primarily a Python ASR toolkit, not necessarily an MCP server. If the listing refers to a community MCP

[yulinlina]

Thanks for the heads-up.

There isn’t any required action on our side for the indexing itself. If you think the badge would be useful for discoverability, the best path is to open a small PR adding it to the README, ideally near other badges or links.

For example:

[![MCP Marketplace](https://img.shields.io/badge/MCP%20Marketplace-Indexed-blueviolet)](https://getlulu.dev/mcps)

A few notes:

• Please make sure the listing description is accurate and does not imply official endorsement.
• We generally prefer to keep README badges limited to directly relevant project/status links.
• Paid SDK/monetization integration is not something we’re planning right now, so no follow-up is needed there.

If you want the badge included, a minimal PR is the easiest way to review and merge it.