Official entry points
The target, category, official website and publishing or integration route. Closed or unavailable routes are excluded or flagged.
Research for MCP-ready products & integrations
25 researched targets.
A clearer next step.
Find candidate places to list your integration, with the publishing route and requirements beside each name.
We research public primary sources across MCP registries, agent frameworks and marketplaces. You receive a reviewed CSV that distinguishes documented facts, compatibility assessments and missing evidence.
Discuss your research briefScope, price and delivery date are agreed before work begins. Sending a brief creates an inquiry, with no charge or paid order.
A list you can work from
The route matters
as much as the name.
The research explains what is documented and what your team would still need to verify or build.
Requirements you can check
Published eligibility, application steps, known fees and restrictions. A free product label is not evidence that publishing is free.
Fit, with the reasoning
A compatibility assessment based on your public API, SDK, MCP server or package. Assessments and proposed work are separate from verified facts.
Gaps made visible
Unverified fees and missing requirements stay marked. If the agreed scope cannot be supported, we discuss it rather than pad the list.
Delivery format
A reviewed CSV, ready for your team.
Target · Category · Organisation domain · Publishing mechanism · Submission URL · Evidence URL · Public contact · Requirements · Integration shape · Notes
Sources reflect what was checked at delivery and can change. A candidate channel is not an approved listing or a tested integration. Building integrations, submitting applications and outreach are outside this research brief. Approval, traffic and sales are not guaranteed.
From brief to handoff
Small scope.
Clear agreement.
- Share the product.
Send a public product page, describe the integration you have and tell us which categories or targets matter.
- Confirm the brief and quote.
We review feasibility and agree the scope, required evidence, price, payment arrangements and delivery date before work starts.
- Receive the reviewed research.
Get the CSV and source links, with compatibility assumptions and evidence gaps clearly marked. Each delivery is reviewed before handoff.
An early track record
One paid research project.
26 targets delivered.
This is a limited starting record. It does not establish repeat demand or an accuracy rate. Every new assignment needs its own scope and source review.
View the public provider profileStart with the brief
Where should your
integration go next?
Email the studio to discuss scope and a quote. Briefs are reviewed manually; availability and timing are confirmed by reply.
Use public links only. Please leave passwords, API keys, customer records and confidential documents out of your email.
Tell us what you are building.
A useful first email includes:
- Product name and a public HTTPS link. What does it do, and who uses it?
- The integration available today. An API, SDK, MCP server, plugin or library, with public documentation if available.
- The target categories. Use the standard MCP mix or describe a different scope.
- Exclusions and required facts. Existing listings, domains to avoid, compatibility questions or publishing restrictions.
- Your requested date and budget. Include a currency if you have a budget in mind.
The button opens your email app. You review and send the message there. If no app opens, copy the address into your email service.
Sending an email does not accept a quote, start work, create a paid order or collect a payment. Scope and funding are confirmed separately.