YourICP
v0.1.3Enrich contacts by email or LinkedIn URL and build targeted B2B audiences.
Endpoint health
online- Last checked
- 11/20/2026, 8:17:53 AM
- Latency
- 204 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.youricp%2Fmcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.youricp/mcp-server": {
"url": "https://mcp.youricp.com/sse"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
13 shown · authentication unknown
activate_login
Activate a login completed in the browser. Call this after signing in at the login page. Automatically retrieves the auth token and activates it for this session — no copy/paste needed.
Schema valid · SHA-256 3872436c21cb…
View input schema
{ "type": "object", "properties": {} }audience_download_run
Get the download link for a completed audience run. Returns a presigned URL the user can click to download their contact list. RENDERING — MANDATORY, VERBATIM: The response contains a download link already formatted as a markdown link with an angle-bracket destination: [Download ...](<https://...>). Present it exactly as returned. Keep the angle brackets around the URL, do NOT percent-encode or decode any query parameters, and do NOT drop, reorder, or truncate any parameter — every response-content-* and X-Amz-* param must be preserved byte-for-byte. Do NOT rewrite it into a code block, a bare URL, or an HTML anchor; emit the markdown link as the backend sent it.
Schema valid · SHA-256 387bcc8dc76d…
View input schema
{ "type": "object", "properties": { "runId": { "type": "string", "description": "The runId returned by audience_start_run or check_payment" } }, "required": [ "runId" ], "$schema": "http://json-schema.org/draft-07/schema#" }audience_get_filters
Fetch all available audience filter categories as an interactive filter picker. Only call this after audience_start has been called and the user chose Option B (interactive filter picker). Do not call this tool to guess or pre-populate filters on behalf of the user. RENDERING — MANDATORY, VERBATIM: The response is usually a complete HTML document. Pass the returned HTML string unchanged to the visualizer/render tool. Do NOT rebuild, restyle, summarize, trim, or hand-author a replacement UI. If the response is plain text instead of an HTML document (this happens on clients that cannot render HTML), simply present that text to the user as-is and let them pick filter values by name — do not look for a visualizer. Render EVERY tab and EVERY chip exactly as received, in the order received, using the exact data-cat and data-val attributes the backend emitted. This includes tabs whose chip list is empty — render the empty tab as-is, do NOT drop it and do NOT invent or backfill chips for it. ALWAYS keep the "Get estimation" button (id="getEstBtn") in the rendered widget. It is the action control the user clicks to run the preview — never remove, hide, rename, or replace it. Do NOT move a chip from the tab/category the backend placed it in. If a value arrives under data-cat="industries", it is rendered and reported under industries — the client must not re-route it to seniority, departments, buying_roles, employee_size, or revenue based on its label. Field placement is the backend's responsibility, not the client's. When the user makes selections, resolve names→keys ONLY via the <script id="filter-key-map"> JSON in the returned HTML, then call audience_preview with those exact keys.
Connections
streamable-http
https://mcp.youricp.com/sse