eyecon

Eyecon: Use the no.1 API for a true caller ID to identify name and see photos. 100% success rate.

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
55%
Naming quality
85%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'get_api_v1_getCountryCode' doesn't follow camelCase/snake_casein get_api_v1_getCountryCode

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~121Tokens (tool definitions)
~306 BTypical response size
Minimal attention impact (0.09% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "eyecon": {
      "url": "https://mcp.jojapi.com/eyecon"
    }
  }
}

Remote endpoints

https://mcp.jojapi.com/eyeconstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_api_v1_getCountryCode

Get list of all country codes. Billing per call: 1 Credits.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_api_v1_search(code, number)

Search for the contact based on phone number and country code. Billing per call: 1 Credits.

Input Schema

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string"
    },
    "number": {
      "type": "string"
    }
  },
  "required": [
    "code",
    "number"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools