Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Victano: EU tenders and grant calls is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
EU tenders and grant calls, matched to your company and qualified, inside the AI you already use
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http victano-eu-tenders-and-grant-calls-mcp https://mcp.victano.com/mcp
# 2 — ask your agent for something these tools do
# connect_start, connect_verify, whoami and 6 more
Victano: EU tenders and grant calls costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VIAll 1 server
victano1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http victano-eu-tenders-and-grant-calls-mcp https://mcp.victano.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Begin authentication. Send the user's work email and your conversation's language ('lt', 'en'…); Victano mails a confirm link and a code. Then call connect_verify(request_id) at once: it waits for the click. No card needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| language | no | — |
Finish signing in: call right after connect_start with no code; it waits for the Confirm click (if it returns waiting, call again; never ask the user). Or pass the code they read you. Returns an api_key (shown once) and, without a connection session, a session to pass on every later call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| code | no | — |
The connected account: tier, persona, corpus freshness, and every limit — what is left in the current window, and the caps that do not renew. Call it when a user asks about limits, when you are unsure whether you are authenticated, or to confirm a setting took.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. The playbook library: how bid professionals actually run this work, from the weekly scan through qualification, eligibility screening, reading a specification, clarification questions, and the proposal skeleton. READ A WORKFLOW BEFORE IMPROVISING A PROCESS. Whole jobs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| persona | no | — | |
| limit | no | How many playbooks to list (jobs always lead); default all. | |
| detail | no | 'compact' (default) or 'full'. | |
| max_chars | no | Hard cap on the answer's size in characters (default 8000). Over it, cards shrink to the essentials, then rows are dropped from the end, and truncated says how to get the rest. | |
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. The complete step-by-step playbook for one workflow id, including the decision gates, the EU procurement specifics that decide eligibility, and the pitfalls that lose bids. Follow it rather than summarising it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflow_id | no | — | |
| id | no | — | |
| name | no | — | |
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. Search open public tenders and EU grant calls by subject, ranked by relevance, with filters for country, CPV, status, deadline, value and region. Use it to find notices worth a decision, then get_opportunity or read_document. Cards are compact (summary_cut marks a c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | What the user is looking for, as they typed it. | |
| queries | no | The same question in the notices' own languages, one phrasing per country in scope; each is ADDED to query and fused as its own ranking. Translate the distinctive trade terms, not the sentence (rese | |
| countries | no | ISO3 ('LTU') or ISO2 ('LT'). Scope by country when you can: EU-wide is ~10x slower. | |
| nuts | no | NUTS2 regions below country level ('DE30', 'LT01'); notices without a NUTS code are excluded. | |
| nuts_strict | boolean | no | — |
| kind | no | — | |
| cpv | no | Any CPV prefix: '45', '452' or a full code. Results show cpv_labels, not codes. | |
| cpv_divisions | no | — | |
| cpv_strict | boolean | no | Sources that publish no CPV (Lithuanian CVP notices, EU grant calls) are INCLUDED and ranked by default; true excludes them. |
| source | no | 'ted', 'cvp', 'ft', 'ee', 'lv', 'hun', … (research_guide lists them). | |
| type | no | 'tender' or 'grant' (use 'grant' when the user asks for grant calls). | |
| contract_nature | no | 'works', 'supplies', 'services'. Sources that publish none are included unless nature_strict=true. | |
| nature_strict | boolean | no | — |
| lang | no | — | |
| exclude_results | boolean | no | true drops award notices for things already decided. |
| status | no | 'open' (default), 'forthcoming' for not-yet-open, 'any' adds expired. | |
| deadline_after | no | ISO date. | |
| deadline_before | no | ISO date. | |
| min_value | no | In EUR, converted from the buyer's currency; notices we cannot price in euros are excluded from a value filter rather than guessed at. | |
| max_value | no | In EUR, converted from the buyer's currency; notices we cannot price in euros are excluded from a value filter rather than guessed at. |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. Full normalised record plus the document inventory. Use before advising on a bid; a search card is not enough. Follow with read_document for eligibility text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opportunity_id | no | — | |
| id | no | — | |
| as_units | boolean | no | Also return the notice as text units (title, notice); for verifiers. |
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. Send feedback about Victano to the team that builds it: a bug, a wrong answer, missing data, a missing feature, a workflow idea, or praise. Every item is read by a person. When to offer it: an answer came back empty or wrong; the user corrected you or the result; a wo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | One of: bug (something failed or errored), wrong_answer (an answer was returned but it was wrong or misleading), missing_data (a document, record or source the user expected is not covered), missing_f |
| what | no | The task and what went wrong or what is needed (3-50000 characters) | |
| expected | no | For a wrong answer: what the right answer or result would have been (up to 20000 characters) | |
| got | no | For a wrong answer: what came back instead (up to 20000 characters) | |
| tool | no | The tool the feedback is about, if one (e.g. the tool that answered wrongly); several: comma-separated | |
| query | no | The query or arguments that produced it; only with the user's OK (up to 5000 characters) | |
| severity | no | low | normal | high | blocking (blocking: the user cannot do their work) | |
| contact_email | no | Only if the user wants a reply: the address to reply to | |
| authored_by | no | user (their words) | agent_drafted (you wrote it, they approved) | agent (your own observation) | |
| confirmed | boolean | no | true once the user approved sending this; required for authored_by user or agent_drafted |
| message | no | Older name for what, kept so earlier callers still work; prefer what | |
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Sign-in required: call connect_start(email) and connect_verify first (free, one email) unless this connection is already signed in. Messages from the Victano team to this person: replies to their feedback, questions about it, service notices and news about the tools they use. action='list' shows the inbox; 'read' with id opens one message and marks it read; 'reply' with id and body answers a messa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | no | list (default) | read | reply | dismiss | snooze | settings | |
| id | no | The message id from list (for read, reply, dismiss, snooze) | |
| body | no | For reply: the person's answer, in their words, only after they approved it (up to 50000 characters) | |
| hours | no | For snooze: how long to put the message away (default 24, at most 720) | |
| settings | no | For settings: the switches to change, e.g. {"email_feedback_replies": false}. Omit to read them. email_digest: a periodic email summary of unread messages (off by default); email_feedback_replies: an | |
| confirmed | boolean | no | For reply: true once the person approved sending these words |
| session | string | no | The session value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAu |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Victano: EU tenders and grant calls or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.4.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest23f9099320ea6b586cd521d1299935cc009ea4ddd19496619e3ddaad16be7489
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| connect_start | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| connect_verify | state-write | state-write: declares readOnlyHint: false |
| whoami | no tags | |
| list_workflows | no tags | |
| get_workflow | no tags | |
| search_opportunities | no tags | |
| get_opportunity | no tags | |
| submit_feedback | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| notifications | untrusted-inputexternal-sink | untrusted-input: keyword "read_message"; external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest23f9099320ea6b58
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Victano: EU tenders and grant calls can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.