Random Profiles

com.random-profilesPublished by random-profiles.comv1.4.4Updated Oct 24, 2026

Generate fake user profiles and companies for tests, seed data, and AI agent demos.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Generates fake user profiles and companies, with photos and logos, for tests, seed data and demos.

What you can do
Generate random user profiles with filters for count, gender, country, age range and field groups, or fetch one by UUID, including profile photos as JPEG or WebP at a chosen size. Generate fake companies with filters for count, industry, country, size and field groups, or fetch one by UUID, with logo size variants. Follow relationship fields to link profiles to companies and colleagues and hydrate the graph. Check API key usage, tier and daily limits. Claim a free API key with an email address on first run.
When to use it
Useful when you need realistic-looking sample people or companies for test fixtures, database seed data, UI mockups or AI agent demos, and want an assistant to produce them on request instead of writing them by hand.
Requirements
Runs locally over stdio, typically via npx, so Node.js is needed. An API key is required: set RANDOM_PROFILES_API_KEY, or let the first request claim a free key using an email address, cached at a config file in the home directory. Network access to the Random Profiles API is needed.
Before you install
The first-run flow asks for an email address, claims a key on your behalf and emails a copy as a receipt; the key is cached locally in a config file. The usage tool returns a support link for paid unlimited access, so paid tiers may be offered. Generated data is synthetic and should not be treated as real personal information.

Installation

In SourceWeft

  1. Open Random Profiles in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

random-profiles-mcp

MCP server for the Random Profiles API — generate fake user profiles and companies directly from AI agents like Claude.

Setup — zero config

Just install the MCP server and talk to it. The first time you ask for profiles, the agent will prompt you for an email once, claim a free key on your behalf, cache it locally, and use it for every future request. The key is also emailed to you as a receipt.

Add to your Claude Code MCP config (.mcp.json):

json
{  "mcpServers": {    "random-profiles": {      "type": "stdio",      "command": "npx",      "args": ["-y", "random-profiles-mcp"]    }  }}

Restart Claude Code and ask "give me 5 random user profiles" — the agent will handle the key handshake automatically. No browser, no copy-paste.

The key is cached at ~/.random-profiles/config.json (mode 0600) so you only do this once per machine.

Prefer to bring your own key?

If you already have an API key (or want to use a specific one), set it via env var and skip the claim flow entirely:

json
{  "mcpServers": {    "random-profiles": {      "type": "stdio",      "command": "npx",      "args": ["-y", "random-profiles-mcp"],      "env": {        "RANDOM_PROFILES_API_KEY": "rp_your_key_here"      }    }  }}

The env var takes precedence over the cached key.

Tools

ToolDescription
claim_api_keyClaim a free API key using an email address (response returns the key; the agent also emails a copy as a receipt). Only used on first run when no key is configured — cached afterward.
get_profilesGet random user profiles with filters (count, gender, country, age range, fields)
get_profileGet a single profile by UUID
get_companiesGet random fake companies with filters (count, industry, country, size, fields)
get_companyGet a single company by UUID
get_random_imageGet a random profile photo (JPEG, optional size)
get_imageGet a specific profile photo by UUID (JPEG, optional size)
get_usageCheck your API key usage, tier, and daily limits (includes a buy-me-a-coffee support_url for unlimited access)

Field Groups

Profiles: name, email, phone, identity, bio, social, physical, job, address, financial, network, documents, vehicle, contact, digital, interests, education, photo, relationships, meta

Companies: name, industry, size, location, contact, social, financial, tech, leadership, legal, operations, product, relationships, meta

The relationships group returns cross-resource UUIDs: profiles have company_uuid + colleague_uuids, companies have employee_uuids. Chain tools together to hydrate the graph (e.g. "give me 5 companies, then their employees").

Image formats

Both get_profiles and get_companies accept an optional photo_format / logo_format argument (jpg or webp). WebP is ~30% smaller than JPG with equivalent perceived quality and is supported by 96%+ of browsers. Default stays jpg for maximum compatibility.

Examples

Profiles

"Give me 5 random US profiles"

"Generate 10 female profiles between ages 25-35 from Germany"

"Get me profiles with only name and email fields"

"Show me a random profile photo"

Companies

"Give me 5 fake Technology companies from the US"

"Generate 10 Healthcare companies with 51-200 employees"

"Get 20 companies with only name, industry, and leadership fields"

"Give me 3 Finance companies from the UK with a fixed seed of 42"

"Give me 10 companies with 128px logos (for an icon grid)"

The logo_size argument on get_companies/get_company picks the size variant in meta.logo_url — same pattern as photo_size on profiles. Valid values: 64, 128, 256, 512, 1024 (default).

Environment Variables

VariableRequiredDescription
RANDOM_PROFILES_API_KEYYesYour API key (get one at random-profiles.com)

See also

License

MIT

Source: README.md at commit 46557ba

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.4.4LatestSep 28, 2026
  2. v1.4.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts