IMEI Generator Skill
The tool
The API generates IMEIs based on a comprehensive Type Allocation Code (TAC) database, with optional filtering by manufacturer brand and support for generating multiple IMEIs.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as IMEIGeneratorSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "IMEIGeneratorSkill",
"arguments": {}
}Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
brand | string | Samsung | Filter by manufacturer brand (e.g., Samsung, Apple, Nokia) |
countPremium | integer | 1 | Number of IMEIs to generate |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"count": 2,
"brand": "Samsung",
"imeis": [
{
"imei": "358398048517203",
"tac": "35839804",
"manufacturer": "Samsung",
"model": "Galaxy Xcover",
"serial": "851720",
"checksum": "3",
"isValid": true
},
{
"imei": "359040029448038",
"tac": "35904002",
"manufacturer": "Samsung",
"model": "SGH-B130",
"serial": "944803",
"checksum": "8",
"isValid": true
}
]
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 2 | Number of IMEIs returned |
brand | string | Samsung | Manufacturer the reporting body identifier belongs to |
imeis | array[2] | list of rows | Array of generated IMEI objects |
imeis.0.imei | string | 358398048517203 | |
imeis.0.tac | string | 35839804 | |
imeis.0.manufacturer | string | Samsung | |
imeis.0.model | string | Galaxy Xcover | |
imeis.0.serial | string | 851720 | |
imeis.0.checksum | string | 3 | |
imeis.0.isValid | boolean | true |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use IMEI Generator Skill
Set up IMEI Generator Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use IMEIGeneratorSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.