Give your AI agents real-time signals

Connect Claude, Cursor, Windsurf, and any MCP-compatible client to Signalbase. Your AI gets access to funding rounds, M&A activity, job changes, hiring data, investors, and company profiles.

Terminal

Click to copy — paste into your terminal to connect Claude Code

Six tools, one endpoint

Every search surface exposed as an MCP tool your agents can call. A credit is only spent when results are delivered.

1 credit

search_funding_signals

Find recently funded companies by round type, sector, and geography

Free with count=true

1 credit

search_acquisition_signals

Track M&A activity and acquisition indicators with signal scores

1 credit

search_job_change_signals

Monitor C-suite and leadership role changes across companies

1 credit

search_hiring_signals

Find open job postings by role, department, location, and team size

Free with count=true

1 credit

search_investors

Search VCs, angels, PE firms with AUM, check sizes, and portfolio data

1 credit

search_companies

Browse company profiles with headcount, growth metrics, and industry

Free with count=true

Bulk enrichment runs over REST, with the same key

POST /api/v2/csv-enrichment enriches up to 1,000 companies with all their signals for 1 credit per job, and polling results is free. It is a REST call rather than an MCP tool, so point your agent at the docs and let it use the same Bearer token.

Connect in 3 minutes

Log in, then Profile → Get API key → Generate. Copy the key and replace YOUR_API_KEY everywhere below.

Fastest route: let your AI do the setup

Paste this into Claude, Cursor or Windsurf. It finds the right config file, edits it without breaking servers you already have, and tells you when to restart.

Please connect me to the Signalbase MCP server.

Server URL: https://mcp.trysignalbase.live
Auth header: Authorization: Bearer YOUR_API_KEY

Find the MCP config file for this app, add Signalbase to it without
breaking any servers already configured, and tell me exactly what to do
to reload. If the file doesn't exist, create it.

Or configure your client by hand:

One command in your terminal. The server speaks streamable HTTP natively, so no wrapper is needed:

claude mcp add signalbase --transport http https://mcp.trysignalbase.live --header "Authorization: Bearer YOUR_API_KEY"

Then run claude mcp list to confirm it is connected.

Check it worked

Ask your AI: "How many hiring signals does Signalbase have in the US? Use count only." The call is free.

You get a total count back in a few secondsWorking. That call was free.
"I don't have that tool"The app didn't reload. Fully quit and reopen it.
"Authentication failed" or 401Key is wrong or has a stray space. Re-copy it from Profile.
Nothing happens for 30+ secondsNode may be missing (Claude Desktop route only). Run node --version; install Node if it errors.

Getting good results

Four habits that separate a clean session from a confusing one.

Ask for job location, and say which kind

Three country filters exist on hiring, and the default one is the widest. Using countries for "roles located in Sweden" returns Swedish companies hiring in Dallas.

countriesJob location OR company HQWidest net, and the default agents reach for
job_countriesJob location only"Engineering roles located in Sweden"
company_countriesCompany HQ only"Swedish companies hiring anywhere"

Always sort by date

Results carry no default date order, so page 1 is not the newest page. Add sort_by="date_posted", sort_order="desc" to every hiring query.

Look companies up by domain, and count first

Company name matching is fuzzy by design, so short names return thousands of rows. The strict fields are company_domain on signals and domain or linkedin_url on companies. Pair them with count=true to size a query for free before paying for rows.

Union your title synonyms

One phrase under-counts a function. Sales Operations, Marketing Operations, Revenue Operations and RevOps are four different result sets for the same job family; search the union when you are sizing a market.

Try these

Paste any of these once you are connected.

Companies that just raised and are already hiring

>Find UK companies that raised in the last 30 days, then check each one's open role count using count only. Rank by number of open roles.

The strongest lead type, and the ranking step is free

European companies expanding into the US

>Find leadership roles where the company is headquartered in Sweden, Germany or the Netherlands but the job is located in the US.

job_countries and company_countries working together

Everything on one company

>For stripe.com, show open roles, recent funding and any acquisitions.

Domain lookups are strict matches, so no fuzzy surprises

Size a market before spending credits

>How many Head of Marketing roles are open in the UK? Count only.

count=true is free on hiring, companies and funding

Limits worth knowing

The honest section. Knowing these saves you a support email.

Response size

Full job and company descriptions come back on every row, so requests over about 25 rows can exceed your AI's context limit. If results look truncated, lower limit or ask your AI to save them to a file and summarise.

Rate limits and pagination

Keep concurrency at 4 calls or fewer or you will see 429s. Paginate with page (100 results per page maximum); offset is not supported.

Two kinds of hiring record

Roles detected from executive posts are usually under two weeks old but carry fewer structured fields. Roles from job boards are older but include job country and company headcount. Filtering on structured fields narrows you to the job-board set, so fresh post-sourced roles drop out.

Troubleshooting

Every symptom we have seen in the wild, with its fix.

Tool not foundThe app didn't reload. Fully quit and reopen it.
401 UnauthorizedBad or expired key. Regenerate it: Profile → Get API key.
Hangs on the first callNode may be missing (Claude Desktop route). Run node --version and install it if that errors.
A filter seems ignoredInvalid enum values can be silently ignored. Check the value against the docs.
429 Too many requestsReduce concurrency to 4 calls or fewer at a time.
Wrong country in resultsYou used countries, which also matches company HQ. Use job_countries for job location.
Results look months oldNo sort applied. Add sort_by="date_posted", sort_order="desc".
Response looks truncatedLarge row payloads. Lower the limit, or ask your AI to save results to a file and summarise.
Company search finds nothingFree-text search doesn't match domains or LinkedIn slugs. Use domain= or linkedin_url=.

Full parameter reference in the API docs.

Edge-deployed

Runs on Cloudflare Workers across 300+ locations. Sub-100ms latency from anywhere.

Real-time data

Signals are verified within minutes. Your AI always has the freshest intelligence.

Pay per signal

1 credit per delivered search. Count mode is free on hiring, companies and funding.

MCP access included in every plan

Ready to connect?

One key, one config block, and your agent is querying live signals three minutes from now.

7-day trial with 500 credits included

MCP server FAQ

Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. Signalbase runs as an MCP server, so any MCP-compatible client can query live signals directly.