[APP] 123RF

**Name of app / service**

123RF — stock photo, vector, audio and video licensing platform (https://www.123rf.com).

I'm on the engineering team at 123RF. We already run a production MCP server and would like 123RF listed in the Pipedream registry so it's reachable through Pipedream's hosted MCP surface. We intend to contribute the components ourselves — this request is the prerequisite step per the PR template's "the app updated in this PR is already integrated" checkbox.

**Link to developer documentation**

- MCP server + connect flow: https://www.123rf.com/mcp
- MCP endpoint: `https://agent.123rf.com/mcp`

Auth is **OAuth 2.0**, discoverable via RFC 9728 / RFC 8414:

- `https://agent.123rf.com/.well-known/oauth-protected-resource`
```json
{
"resource": "https://agent.123rf.com/mcp",
"authorization_servers": ["https://www.123rf.com/apicore-index"],
"scopes_supported": ["mcp"],
"bearer_methods_supported": ["header"]
}
```
- Authorization server metadata — `https://www.123rf.com/apicore-index/.well-known/oauth-authorization-server`
```json
{
"issuer": "https://www.123rf.com/apicore-index",
"authorization_endpoint": "https://www.123rf.com/apicore-index/oauth/authorize",
"token_endpoint": "https://www.123rf.com/apicore-index/oauth/token",
"registration_endpoint": "https://www.123rf.com/apicore-index/oauth/register",
"scopes_supported": ["mcp"],
"response_types_supported": ["code"],
"grant_types_supported": ["authorization_code", "refresh_token", "client_credentials"],
"code_challenge_methods_supported": ["S256"],
"token_endpoint_auth_methods_supported": ["none", "client_secret_post"]
}
```

**Is lack of support preventing you from moving forward, or do you have a workaround?**

Blocking, with no workaround. Pipedream users currently have no way to reach 123RF. Our own users can add our MCP server as a custom connector in Claude or Cursor, but that path doesn't exist inside Pipedream — Connect/MCP users can only reach apps in your registry. We can't open the components PR until the app record and its auth strategy exist on your side.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

We'll contribute these ourselves — no work needed from your team beyond the app record. First submission is actions only (no sources; we don't yet have a polling or webhook contract worth shipping):

| Action | Key | Description |
| --- | --- | --- |
| Search Assets | `_123rf-search-assets` | Keyword search across photos, vectors, audio and video |
| Download Stock | `_123rf-download-stock` | Download a licensed asset; deducts once against the member's plan |
| Get Stock Balance | `_123rf-get-stock-balance` | Read the connected member's plan and remaining quota |

These mirror the three tools our production MCP server already exposes.

**Maintenance:** 123RF will contribute and maintain the component — version bumps, API changes and review replies.

One naming question: your registry has no component directory starting with a digit — the convention is an underscore prefix (`_1crm`, `_10000ft`, `_2chat`). We've assumed the slug **`_123rf`** and keyed the actions accordingly. Please confirm, or tell us the slug you assign and we'll match it.

Start by reviewing the Pipedream registry's app-record and authentication conventions, along with the PR template's requirement that the app is already integrated. Confirm the `_123rf` slug and OAuth strategy using the supplied MCP endpoint and metadata; done means the 123RF app record exists so the team can submit its components PR.

Written by the indexing model from the issue text.