Rift is **agent-native deep linking infrastructure**. This MCP server exposes the Rift API so any MCP client can create, inspect, and manage deep links programmatically. Each Rift link is a short URL with first-class `agent_context` — structured metadata that lets AI agents understand the destination, intended action, and parameters without rendering a page. Install attribution, click tracking, and conversion events come built in. ## What you can do - Create deep links from inside an LLM workflow with `create_link` - Attach `agent_context` so downstream agents can act on the URL - Resolve, update, and delete links through MCP tools - Track clicks, installs, and conversions across iOS, Android, and web - Migrate off Firebase Dynamic Links (deprecated August 2025) ## MCP tools exposed - `create_link` — Create a deep link with target, app URI, social preview, and `agent_context` - `get_link` — Fetch a link and its metadata - `list_links` — List links for the authenticated tenant - `update_link` — Modify destination, agent context, or social preview - `delete_link` — Remove a link ## Authentication Streamable-HTTP transport. Pass an `rl_live_` API key as the `x-api-key` header. Free tier available at https://riftl.ink/account. ## About Rift Rift is a deep linking and attribution API for the agent era. Built as a developer-first replacement for Firebase Dynamic Links, with native MCP support and the open Agent Deep Link Specification v0.1. Learn more: https://riftl.ink Docs: https://riftl.ink/docs/mcp
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (2102 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 8 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 52% of peers
- This listing 81 · peer median 81
- Latency
- Faster than 29% of peers
- This listing 511 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/terentiev-andrei/rift-links/mcpcurl -X POST https://server.smithery.ai/terentiev-andrei/rift-links/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'